| 2 | Approval of Agenda | |
|---|---|---|
| R1-2110750 | Draft Agenda of RAN1#107-e meeting | RAN1 Chair |
| R1-2110752 | RAN1#107-e Meeting Invitation, Timelines, Scope, Process | RAN1 Chair, ETSI MCC |
| R1-2110753 | Additional Guidelines for RAN1#107-e-Meeting Management | RAN1 Chair |
| R1-2111194 | Draft Agenda of RAN1#107-e meeting | RAN1 Chair |
| 4 | Approval of Minutes from previous meetings | |
| R1-2110751 | Report of RAN1#106bis-e meeting | ETSI MCC |
| 5 | Incoming Liaison Statements | |
| R1-2110754 | Reply LS on RSS-based RSRQ | RAN4, Huawei |
| R1-2110755 | LS to RAN1 on UL skipping with LCH-based prioritization | RAN2, vivo |
| R1-2110756 | LS on initial state of elements controlled by MAC CEs | RAN2, Huawei |
| R1-2110757 | LS on PDCCH Blind Detection in CA | RAN2, Huawei |
| R1-2110758 | LS on RMSI reception based on non-zero search space | RAN2, OPPO |
| R1-2110759 | LS Reply on UE Power Saving | SA2, Huawei |
| R1-2110760 | LS on PC5 DRX for ProSe | SA2, LG Electronics |
| R1-2110843 | Views on RAN2 LS for inter-cell BM and multi-TRP in R17 | Huawei, HiSilicon |
| R1-2110905 | [DRAFT] Reply LS on RMSI reception based on non-zero search space | ZTE |
| R1-2110906 | [Draft] Reply LS on PDCCH Blind Detection in CA | ZTE |
| R1-2110969 | Draft reply LS on initial state of elements controlled by MAC CEs | vivo |
| R1-2110970 | Discussion on RAN2 LS on RMSI reception based on non-zero search space | vivo |
| R1-2110971 | Discussion on RAN2 LS on PDCCH Blind Detection in CA | vivo |
| R1-2111208 | Draft Reply LS on initial state of elements controlled by MAC CEs | CATT |
| R1-2111334 | Discussion on RMSI reception based on non-zero search space | OPPO |
| R1-2111335 | Reply LS on RMSI reception based on non-zero search space | OPPO |
| R1-2111709 | Discussion on RAN2 LS on blind detection in CA | Samsung |
| R1-2111710 | Draft reply LS on initial state of elements controlled by MAC CEs | Samsung |
| R1-2111789 | [Draft] Reply LS on initial state of elements controlled by MAC CEs | ZTE |
| R1-2111843 | Discussion on RAN4 LS R1-2108704 on beam information of PUCCH Scell in PUCCH SCell activation procedure | Apple |
| R1-2111936 | Views on initial state of elements controlled by MAC CEs | Huawei, HiSilicon |
| R1-2111937 | Draft Reply LS on initial state of elements controlled by MAC CEs | Huawei, HiSilicon |
| R1-2111938 | Views on RMSI reception based on non-zero search space | Huawei, HiSilicon |
| R1-2112184 | Discussion on LS on beam information of PUCCH SCell in PUCCH SCell activation procedure | Qualcomm Incorporated |
| R1-2112185 | Discussion on UL MIMO Coherence capability | Qualcomm Incorporated |
| R1-2112186 | Draft Reply LS on initial state of elements controlled by MAC CEs | Qualcomm Incorporated |
| R1-2112187 | Discussion on RMSI reception based on non-zero search space | Qualcomm Incorporated |
| R1-2112311 | Discussion on RAN2 LS on broadcast session delivery about MCCH design | MediaTek Inc. |
| R1-2112328 | Discussion regarding LS reply on initial state of elements controlled by MAC CEs | Ericsson |
| R1-2112360 | On RMSI reception based on non-zero search space | Ericsson |
| R1-2112373 | On RMSI reception based on non-zero search space | Nokia, Nokia Shanghai Bell |
| R1-2112374 | [DRAFT] Response LS on RMSI reception based on non-zero search space | Nokia, Nokia Shanghai Bell |
| R1-2112402 | Discussion on beam information of PUCCH SCell in PUCCH SCell activation procedure | Huawei, HiSilicon |
| R1-2112406 | Discussion on LS on Status Update on XR Traffic | Huawei, HiSilicon |
| R1-2112407 | Draft reply LS on PDCCH Blind Detection in CA | Huawei, HiSilicon |
| R1-2112409 | Draft reply LS on UL skipping with LCH prioritization | Huawei, HiSilicon |
| R1-2112534 | Incoming LS handling for RAN1#107-e | RAN1 Chair |
| R1-2112593 | Reply LS on use of NCD-SSB for RedCap UE | RAN4, ZTE Corporation |
| R1-2112594 | Reply LS on TA-based propagation delay compensation | RAN4, Nokia |
| R1-2112595 | LS on UE capability for supporting single DCI transmission schemes for multi-TRP | RAN4, Apple |
| R1-2112599 | Reply LS on the use of NCD-SSB instead of CD-SSB for RedCap UEs | RAN2, Ericsson |
| R1-2112607 | Reply LS on time gap information in SCI | RAN2, OPPO |
| R1-2112608 | Reply LS on SL resource selection with DRX | RAN2, Lenovo |
| R1-2112609 | Response LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#105-e | RAN2, Intel |
| R1-2112610 | Response LS on Positioning Reference Units (PRUs) for enhancing positioning performance | RAN2, Qualcomm, CATT |
| R1-2112629 | LS on MPE information signalling | RAN2, Nokia |
| R1-2112630 | Reply LS on the physical layer aspects of small data transmission | RAN2, ZTE |
| R1-2112631 | LS on NR-U channel information and procedures | RAN3, Samsung |
| R1-2112632 | Reply LS on TCI State Update for L1/L2-Centric Inter-Cell Mobility to RAN3 | RAN3, ZTE |
| R1-2112633 | Reply LS on location estimates in local co-ordinates | RAN3, Huawei |
| R1-2112637 | LS on MBS broadcast reception on SCell and non-serving cell | RAN2, Huawei |
| R1-2112670 | Reply to LS on broadcast of NTN GW or gNB position | SA3, Ericsson |
| R1-2112671 | Reply LS on PUCCH and PUSCH repetition | RAN4, Qualcomm |
| R1-2112672 | LS on PEMAX for NR-V2X | RAN4, Huawei, CATT |
| R1-2112673 | Reply LS on NTN UL time and frequency synchronization requirements | RAN4, Xiaomi |
| R1-2112674 | Reply LS on Inter-donor migration for IAB enhancement | RAN4, ZTE Corporation |
| R1-2112675 | Reply LS on combination of open and closed loop TA control in NTN | RAN4, Qualcomm |
| R1-2112676 | LS on interruption for PUCCH SCell activation in invalid TA case | RAN4, MediaTek, CATT |
| R1-2112681 | [Draft] Reply LS on RMSI reception based on non-zero search space | Moderator (OPPO) |
| R1-2112765 | Reply LS on RMSI reception based on non-zero search space | RAN1, OPPO |
| R1-2112856 | Summary of email discussion [107-e-AI5-LSs-03] on reply LS to R1-2108704 | Moderator (Huawei) |
| R1-2112857 | Draft reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure | Huawei |
| R1-2112858 | Reply LS on beam information of PUCCH SCell in PUCCH SCell activation procedure | RAN1, Huawei |
| R1-2112860 | Reply LS on initial state of elements controlled by MAC CEs | RAN1, Huawei |
| R1-2112871 | Summary of discussions on initial state of elements controlled by MAC CEs | Moderator (Huawei) |
| R1-2112873 | Summary of email discussion [107-e-AI5-LSs-02] on reply LS to R1-2110758 | Moderator (OPPO) |
| 5.1 | RAN1 Aspects for RF requirements for NR frequency range 1 (FR1) | |
| R1-2110795 | Discussions on enhancements for UL Tx switching | Huawei, HiSilicon |
| R1-2110904 | Remaining issues for Rel-17 UL Tx switching | ZTE |
| R1-2110972 | Remaining issues on Rel-17 Tx switching enhancements | vivo |
| R1-2111288 | Discussion on Rel-17 Tx switching enhancement | OPPO |
| R1-2112188 | Discussion on R17 UL Tx switching | Qualcomm Incorporated |
| R1-2112826 | [107-e-NR-R17-TxSwitching-01] Summary of email discussion on Rel-17 uplink Tx switching | Moderator (China Telecom) |
| R1-2112898 | RAN1 agreements for Rel-17 Tx switching | WI rapporteur (China Telecom) |
| 5.2 | RAN1 Aspects for NR small data transmissions in INACTIVE state | |
| R1-2110774 | RAN1 aspects for NR small data transmissions in INACTIVE state | Ericsson |
| R1-2110812 | Physical layer aspects of CG-SDT | Huawei, HiSilicon |
| R1-2110973 | Remaining RAN1 impacts for small data transmission | vivo |
| R1-2111083 | Discussion on physical layer aspects of small data transmission | Spreadtrum Communications |
| R1-2111356 | Discussion on the remaining physical layer issues of small data transmission | ZTE, Sanechips |
| R1-2111379 | Remaining issues of physical layer aspects for SDT | Sony |
| R1-2111473 | Discussion on physical layer aspects of small data transmission | Intel Corporation |
| R1-2111539 | Physical layer aspects for NR small data transmissions in INACTIVE state | Xiaomi |
| R1-2111711 | Discussion on physical layer aspects for NR small data transmissions in INACTIVE state | Samsung |
| R1-2111844 | Discussion on physical layer aspects of small data transmission | Apple |
| R1-2112044 | Discussion on physical layer aspects of small data transmission | LG Electronics |
| R1-2112189 | Draft reply LS on the physical layer aspects of small data transmission | Qualcomm Incorporated |
| R1-2112779 | Summary on the physical layer aspects of small data transmission | Moderator(ZTE) |
| R1-2112780 | Comments collection on RRC parameters for small data transmission | Moderator(ZTE) |
| R1-2112781 | [Draft] Reply LS on the physical layer aspects of small data transmission | Moderator(ZTE) |
| R1-2112782 | Reply LS on the physical layer aspects of small data transmission | RAN1, ZTE |
| R1-2112985 | NR small data transmissions in INACTIVE state | Nokia |
| R1-2112987 | Introduction of small data transmission in RRC_INACTIVE state for NR | Samsung |
| 6 | E-UTRA Maintenance | |
| R1-2111064 | Discussion on HARQ bundling for LTE-M MTB scheduling in FDD | ZTE, Sanechips |
| R1-2111065 | Clarification on HARQ bundling for LTE-M MTB scheduling in FDD | ZTE, Sanechips |
| R1-2112365 | Clarification on NPDSCH and NPDCCH starting position for TDD NB-IoT | Ericsson |
| R1-2112366 | Clarification on NPDSCH and NPDCCH starting position for TDD NB-IoT | Ericsson |
| R1-2112378 | Fallback DCI for eMTC | Nordic Semiconductor ASA |
| R1-2112536 | RAN1#107-e preparation phase initial summary on E-UTRA Rel 8-16 CRs | Ad-Hoc Chair (CMCC) |
| R1-2112634 | Fallback DCI for eMTC | Moderator (Nordic Semiconductor ASA), Ericsson |
| R1-2112635 | Fallback DCI for eMTC | Moderator (Nordic Semiconductor ASA), Ericsson |
| R1-2112713 | Clarification on HARQ bundling for LTE-M MTB scheduling in FDD | Moderator (ZTE), Sanechips, Ericsson, Lenovo, Motorola Mobility |
| R1-2112717 | Summary on [107-e-LTE-6CRs-01] | Moderator (ZTE) |
| R1-2112786 | Session notes for 6 (Maintenance of E-UTRA Releases 8-16) | Ad-Hoc Chair (CMCC) |
| R1-2112831 | Moderator summary on [107-e-LTE-6CRs-02] | Moderator (Nordic Semiconductor ASA) |
| 7.1 | Maintenance of Release 15 NR | |
| R1-2110799 | Correction on the determination of the number of part 2 CSI report | Huawei, HiSilicon |
| R1-2110869 | Correction on the description of SSBRI report in TS 38.214 | Huawei, HiSilicon |
| R1-2110870 | Correction on data and control multiplexing | Huawei, HiSilicon |
| R1-2110965 | Discussion on SRS carrier switching | ZTE |
| R1-2111128 | Draft CR on collision between UL transmission scheduled by RAR UL grant and DL reception configured by high layer | vivo |
| R1-2111206 | Discussion on SRS carrier switching | vivo |
| R1-2111207 | Editorial corrections on CCE to REG mapping | CATT |
| R1-2111209 | Correction on n_HARQ determination for PUCCH power control | CATT |
| R1-2111210 | Correction on n_HARQ determination for PUCCH power control | CATT |
| R1-2111211 | Correction on determination of TDRA table to be used for PUSCH | CATT |
| R1-2111212 | Correction on determination of TDRA table to be used for PUSCH | CATT |
| R1-2111213 | Correction on initial value determination of TPC accumulation for PUCCH power control | CATT |
| R1-2111214 | Correction on initial value determination of TPC accumulation for PUCCH power control | CATT |
| R1-2111361 | Discussion on HARQ-ACK multiplexing on PUSCH | ZTE |
| R1-2111446 | Alignment CR on DMRS abbreviation for 38.212 | vivo |
| R1-2111447 | Alignment CR on DMRS abbreviation for 38.213 | vivo |
| R1-2111448 | Alignment CR on DMRS abbreviation for 38.214 | vivo |
| R1-2111474 | Discussion on SRS carrier switching | Intel Corporation |
| R1-2111669 | draftCR on semi-persistent CSI reporting on PUSCH in TS 38.214 (Rel-15) | Ericsson |
| R1-2111670 | draftCR on semi-persistent CSI reporting on PUSCH in TS 38.214 (Rel-16) | Ericsson |
| R1-2111712 | Discussion on ambiguity for SRS carrier switching. | Samsung |
| R1-2111783 | Maximum data rate limit in TB selection | Nokia, Nokia Shanghai Bell |
| R1-2111784 | HARQ-ACK muxing on PUSCH without PUCCH | Nokia, Nokia Shanghai Bell |
| R1-2111785 | PUCCH resource and resource set selection for HARQ-ACK and P-CSI multiplexing | Nokia, Nokia Shanghai Bell |
| R1-2111845 | Discussion and clarification on maximum UCI size before UCI omission | Apple |
| R1-2111846 | Discussion and clarification on CSI report during SCell activation | Apple |
| R1-2111847 | Discussions on PUSCH UCI Multiplexing without HARQ-ACK PUCCH | Apple |
| R1-2111920 | Discussion on the UCI multiplexing without PUCCH | Huawei, HiSilicon |
| R1-2111921 | Correction on the determination of the number of part 2 CSI report (mirrored to Rel-16) | Huawei, HiSilicon |
| R1-2112088 | Discussion on PUSCH without UL-SCH and with FDM indication | NTT DOCOMO, INC. |
| R1-2112190 | Discussion on RI bitwidth and UCI mapping for non-PMI based CSI feedback | Qualcomm Incorporated |
| R1-2112191 | Discussion on SRS carrier switching | Qualcomm Incorporated |
| R1-2112192 | Discussion on HARQ-ACK multiplexing on PUSCH without PUCCH | Qualcomm Incorporated |
| R1-2112292 | On two DCIs in the same slot for BWP switch | MediaTek Inc. |
| R1-2112293 | Clarification on PUSCH with UCI Only and DMRS Multiplexing | MediaTek Inc. |
| R1-2112334 | Draft CR on Type I and Type II CSI feedback | CATT |
| R1-2112400 | Correction on the description of CSI-RS RE mapping in TS 38.211 | Huawei, HiSilicon |
| R1-2112403 | Correction on rate-matching for PDSCH with SPS in TS38.214 | Huawei, HiSilicon |
| R1-2112404 | Correction on PDCCH detection for common search space set in TS38.213 | Huawei, HiSilicon |
| R1-2112413 | Correction on prioritization rules of SRS carrier switching | Huawei, HiSilicon |
| R1-2112535 | Rel-15 NR maintenance handling for RAN1#107-e | RAN1 Chair |
| R1-2112574 | [107-e-NR-7.1CRs-08] Issue#15 Email discussion summary | Moderator (Nokia) |
| R1-2112625 | Summary of [107-e-NR-7.1CRs-14] Miscellaneous corrections on NR | Moderator (CATT) |
| R1-2112628 | Summary of [107-e-NR-7.1CRs-03]: Correction on data and control multiplexing | Moderator (Huawei) |
| R1-2112657 | Summary of [107-e-NR-7.1CRs-05] | Moderator (vivo) |
| R1-2112666 | Summary for [107-e-NR-7.1CRs-11] #18 PUSCH DMRS with UCI Only | Moderator (MediaTek Inc.) |
| R1-2112684 | Summary of [107-e-NR-7.1CRs-09] Issue#16 Discussion and clarification on maximum UCI size before UCI omission | Moderator (Apple Inc.) |
| R1-2112685 | Summary of [107-e-NR-7.1CRs-10] Issue#17 Discussion and clarification on CSI report during SCell activation | Moderator (Apple Inc.) |
| R1-2112709 | Summary of [107-e-NR-7.1CRs-07] on semi-persistent CSI reporting on PUSCH in TS 38.214 | Moderator (Ericsson) |
| R1-2112710 | Correction on semi-persistent CSI reporting on PUSCH | Moderator (Ericsson), Apple |
| R1-2112711 | Correction on semi-persistent CSI reporting on PUSCH | Moderator (Ericsson), Apple |
| R1-2112738 | Summary on [107-e-NR-7.1CRs-15] | Moderator (Samsung) |
| R1-2112745 | Draft CR on TS 38.214 Correction on semi-persistent CSI reporting on PUSCH | Moderator (Ericsson), Apple |
| R1-2112746 | Draft CR on TS 38.214 Correction on semi-persistent CSI reporting on PUSCH | Moderator (Ericsson), Apple |
| R1-2112770 | Clarify UCI bitwidth and UCI mapping order for non-PMI based CSI feedback | Moderator (Qualcomm Incorporated), ZTE, Ericsson, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2112771 | Clarify UCI bitwidth and UCI mapping order for non-PMI based CSI feedback | Moderator (Qualcomm Incorporated), ZTE, Ericsson, Huawei, HiSilicon, Nokia, Nokia Shanghai Bell |
| R1-2112772 | Summary of [107-e-NR-7.1CRs-12] discussion on UCI bitwidth and UCI mapping for non-PMI CSI feedback | Moderator (Qualcomm Incorporated) |
| R1-2112817 | Summary of [107-e-NR-7.1CRs-04] Issue#4: Discussion on SRS carrier switching | Moderator (Huawei) |
| R1-2112852 | Rel-15 editorial corrections for TS 38.214 | Nokia, Nokia Shanghai Bell |
| R1-2112853 | Rel-15 editorial corrections for TS 38.214 (mirrored to Rel-16) | Nokia, Nokia Shanghai Bell |
| R1-2112859 | Summary for [107-e-NR-7.1CRs-6] Issue #10: Discussion on HARQ-ACK multiplexing on PUSCH | Moderator (Apple) |
| R1-2112866 | Rel-15 editorial corrections for TS 38.212 | Huawei |
| R1-2112867 | Rel-15 editorial corrections for TS 38.212 (mirrored to Rel-16) | Huawei |
| R1-2112872 | Summary of discussions on correction of description of SSBRI report in TS 38.214 | Moderator (Huawei) |
| R1-2112874 | Summary of [107-e-NR-7.1CRs-01]: Correction on the determination of the number of part 2 CSI report | Moderator (Huawei) |
| R1-2112875 | Summary of [107-e-NR-7.1CRs-13]: Correction on PDCCH detection for common search space set in TS38.213 | Moderator (Huawei) |
| R1-2112893 | Correction to CCE-to-REG mapping and CSI-RS mapping | Ericsson |
| R1-2112894 | Correction to CCE-to-REG mapping and CSI-RS mapping | Ericsson |
| 7.2 | Maintenance of Release 16 NR | |
| R1-2112854 | Rel-16 editorial corrections for TS 38.214 | Nokia, Nokia Shanghai Bell |
| R1-2112865 | Rel-16 editorial corrections for TS 38.213 | Samsung |
| R1-2112868 | Alignment CR for TS 38.212 | Huawei |
| R1-2112870 | Rel-16 editorial corrections for TS 38.213 | Samsung |
| R1-2112888 | Alignment CR for TS 38.202 | Qualcomm |
| R1-2112895 | Correction to VRB-to-PRB mapping for DCI format 1_2 | Ericsson |
| R1-2112964 | Alignment CR for TS 37.213 | Ericsson |
| 7.2.1 | Maintenance of Two step RACH for NR | |
| R1-2111357 | Editorial correction on the slot configuration of type-2 random access | ZTE, Sanechips |
| R1-2111358 | FL summary on the maintenance of 2-step RACH | Moderator (ZTE) |
| R1-2112824 | Session notes for 7.2.1 (Maintenance of Two step RACH for NR) | Ad-Hoc Chair (CMCC) |
| 7.2.2 | Maintenance of NR-based Access to Unlicensed Spectrum | |
| R1-2110822 | Changes of channel access procedure in TS 37.213 according to MIIT regulation | Huawei, HiSilicon |
| R1-2110823 | Discussion on the impact of MIIT consultation to channel access procedure | Huawei, HiSilicon |
| R1-2110824 | Changes of channel access types tables in TS 38.212 | Huawei, HiSilicon |
| R1-2110825 | Corrections on CG-UCI multiplexing in TS38.212 | Huawei, HiSilicon |
| R1-2110826 | Discussion on the frequency hopping for single/multi PUSCH transmission | Huawei, HiSilicon |
| R1-2110974 | Discussion on channel access procedures for consecutive UL transmissions | vivo |
| R1-2110975 | Correction on channel access procedures for consecutive UL transmission(s) | vivo |
| R1-2110976 | Draft CR on 38.213 on HARQ-ACK codebook determination | vivo |
| R1-2110977 | Discussions on frequency hopping for PUSCH,PUCCH and SRS | vivo |
| R1-2110978 | Draft CR on 38.214 on frequency hopping for multi-PUSCH scheduling by a single DCI | vivo |
| R1-2111082 | Correction on slot configuration in TS 38.213 | ZTE, Sanechips |
| R1-2111339 | Correction on Type-3 HARQ-ACK codebook | OPPO |
| R1-2111340 | Draft CR for correction on unit of CP extension | OPPO |
| R1-2111461 | UL Transmissions in Wideband Operation | Ericsson, Nokia, NSB, LG Electronics, Qualcomm, Huawei, HiSilicon |
| R1-2111462 | Discussion on LS from RAN4 on measuring CSI-RS during SCell activation | Ericsson |
| R1-2111714 | Correction on usage of subCarrierSpacingCommon for unlicensed | Samsung |
| R1-2111927 | Changes of channel access procedure in TS 37.213 | Huawei, HiSilicon |
| R1-2112294 | On additional PDSCH DM-RS dropping with double symbol | MediaTek Inc. |
| R1-2112350 | Correction on UL channel access procedure Type 2A/2B/2C | Lenovo, Motorola Mobility, ZTE, Sanechips, Xiaomi, Intel, OPPO |
| R1-2112461 | Preparation phase email discussion summary for Rel.16 NR-U | Moderator (Qualcomm) |
| R1-2112596 | Summary of [107-e-NR-NRU-04] Email discussion/approval on UL Transmissions in Wideband Operation | Moderator (Ericsson) |
| R1-2112618 | Email discussion summary [107-e-NR-NRU-05] | Moderator (Qualcomm) |
| R1-2112677 | Summary of [107-e-NR-NRU-01] | Moderator (Huawei) |
| R1-2112678 | Summary of [107-e-NR-NRU-02] | Moderator (Huawei) |
| R1-2112718 | [Draft CR] UL transmissions in wideband operation | Moderator (Ericsson), Nokia, NSB, LG Electronics, Qualcomm, Huawei, HiSilicon, OPPO |
| R1-2112719 | UL transmissions in wideband operation | Moderator (Ericsson), Nokia, NSB, LG Electronics, Qualcomm, Huawei, HiSilicon, OPPO |
| R1-2112750 | Changes of channel access types tables in TS 38.212 | Moderator (Huawei), Ericsson, Lenovo |
| R1-2112751 | Changes of channel access procedure in TS 37.213 according to MIIT regulation | Moderator (Huawei), Lenovo, Nokia, Ericsson, Intel |
| R1-2112752 | Corrections on CG-UCI multiplexing in TS38.212 | Huawei, HiSilicon |
| R1-2112787 | Session notes for 7.2.2 (Maintenance of NR-based Access to Unlicensed Spectrum) | Ad-Hoc Chair (Huawei) |
| R1-2112811 | Summary of Email discussion on [107-e-NR-NRU-03] | Moderator (vivo) |
| R1-2112822 | CR on TS 38.213 on frequency hopping for PUCCH | Moderator (vivo), Huawei, HiSilicon, Ericsson, Lenovo, Motorola Mobility |
| R1-2112823 | CR on TS 38.214 on frequency hopping for PUSCH and SRS | Moderator (vivo), Huawei, HiSilicon, Ericsson, Lenovo, Motorola Mobility |
| 7.2.4 | Maintenance for 5G V2X with NR sidelink | |
| R1-2110842 | Correction on processing time for simultaneous SL and UL transmissions/receptions | Huawei, HiSilicon |
| R1-2110979 | Draft CR on TS 38.211 on the timing of reference radio frame | vivo |
| R1-2110980 | Alignment CR on TS 38.213 on SL HARQ-ACK codebook | vivo |
| R1-2110981 | Alignment CR on TS 38.214 on SL CSI reporting | vivo |
| R1-2110982 | Clarification on UCI and SL HARQ-ACK | vivo |
| R1-2110983 | Clarification on SL HARQ-ACK for an incomplete PSFCH period | vivo |
| R1-2110984 | Clarification on SL HARQ-ACK reporting | vivo |
| R1-2110985 | Clarification on UE behavior in case of HARQ RTT restriction violation | vivo |
| R1-2111215 | Draft CR for Rel-16 V2X | CATT, GOHIGH |
| R1-2111296 | Draft CR on RRC parameter for higher layer filtered sidelink RSRP in PSSCH power control | OPPO |
| R1-2111297 | Draft CR for RRC parameters in TS 38.214 | OPPO |
| R1-2111298 | Draft CR for Corrections for PSFCH power control in TS 38.213 | OPPO |
| R1-2111299 | Draft CR for Corrections for Prioritizations for sidelink and uplink transmissions/receptions in TS 38.213 | OPPO |
| R1-2111475 | Draft CR on SL HARQ-ACK feedback reporting to gNB | Intel Corporation, Ericsson, LGE, NTT DOCOMO, Bosch, Qualcomm |
| R1-2111640 | Correction on SL CSI-RS | ZTE, Sanechips |
| R1-2111697 | Editorial correction on parameter name for SL slot configuration in TS 38.213 | NEC |
| R1-2111698 | Editorial correction on parameter name for SL slot configuration in TS 38.214 | NEC |
| R1-2111848 | Correction on Higher Layer Parameters | Apple |
| R1-2112009 | Clarification on the condition to trigger re-evaluation in mode 2 | Sharp |
| R1-2112010 | Correction on priority field value in congestion control for mode 2 | Sharp |
| R1-2112193 | Draft CR on Reserved-bit Values | Qualcomm Incorporated |
| R1-2112332 | Draft CR on editorial changes for RRC parameter names and unclear reference | Nokia, Nokia Shanghai Bell |
| R1-2112333 | Draft CR on editorial changes for RRC parameter names | Nokia, Nokia Shanghai Bell |
| R1-2112655 | Summary of [107-e-NR-5G_V2X-01] on miscellaneous corrections on 5G V2X for TS38.213 | Moderator (vivo) |
| R1-2112656 | Draft editorial changes in summary of [107-e-NR-5G_V2X-01] on miscellaneous corrections on 5G V2X for TS38.213 | Moderator (vivo) |
| R1-2112658 | Summary of [107-e-NR-5G_V2X-05] Clarification on SL HARQ-ACK reporting (R1-2110984) | Moderator (vivo) |
| R1-2112659 | Summary of [107-e-NR-5G_V2X-04] Clarification on UCI and SL HARQ-ACK (R1-2110982) | Moderator (vivo) |
| R1-2112691 | Summary of [107-e-NR-5G_V2X-02] Discussion on miscellaneous corrections on 5G V2X for TS38.214 | Moderator (NEC) |
| R1-2112701 | Outcome of email discussion [107-e-NR-5G_V2X-07] | Moderator (Intel Corporation) |
| R1-2112702 | CR on SL HARQ-ACK feedback reporting to gNB | Moderator (Intel Corporation), Ericsson, LGE, NTT DOCOMO, Bosch, Qualcomm, vivo, ZTE, Sanechips, CATT, GOHIGH, Sharp, Huawei, HiSilicon, OPPO, Samsung |
| R1-2112721 | Clarification on UCI and SL HARQ-ACK | Moderator(vivo), NTT DOCOMO, ZTE, Sanechips |
| R1-2112730 | Summary of [107-e-NR-5G_V2X-06] | Moderator (Sharp) |
| R1-2112731 | Correction on mapping between priority field value and priority value in SCI format 1-A | Moderator (Sharp), ZTE, Sanechips, OPPO |
| R1-2112732 | Correction on priority order in power control for PSFCH | Moderator (Sharp), OPPO, ZTE, Sanechips |
| R1-2112879 | Summary of [107-e-NR-5G_V2X-03] Correction on processing time for simultaneous SL and UL transmissions/receptions (R1-2110842) | Moderator (Huawei) |
| 7.2.5 | Maintenance of Physical Layer Enhancements for NR URLLC (Incl. maintenance for IIoT) | |
| R1-2110813 | Discussion on PDCCH Blind Detection in CA | Huawei, HiSilicon |
| R1-2110814 | Remaining issues on UL prioritization and UL skipping | Huawei, HiSilicon |
| R1-2110815 | Remaining issues on UCI multiplexing and prioritization | Huawei, HiSilicon |
| R1-2110816 | Correction on RRC parameter name for UL cancellation indication | Huawei, HiSilicon |
| R1-2110817 | Correction of Downlink Reception types | Huawei, HiSilicon |
| R1-2110907 | Discussion on PDSCH processing timeline for DCI format 1_2 | ZTE |
| R1-2110908 | CR on interleaved VRB-to-PRB mapping corresponding to DCI format 1_2 | ZTE |
| R1-2110909 | Discussion on intra-UE multiplexing in Rel-16 URLLC | ZTE |
| R1-2110986 | Maintenance on intra-UE prioritization and multiplexing | vivo |
| R1-2110987 | Draft 38.214 CR on SRS resource set trigger for DCI format 0_2 | vivo |
| R1-2110988 | Discussion on issues related to SRS resource sets configured for DCI format 0_1 and DCI format 0_2 | vivo |
| R1-2111184 | UE PDSCH Processing Time for DCI Format 1_2 | Ericsson |
| R1-2111185 | UE Procedures for UCI Multiplexing and Prioritization | Ericsson |
| R1-2111186 | Intra-UE Multiplexing/Prioritization and UL Skipping | Ericsson |
| R1-2111187 | PUCCH Multiplexing with SPS HARQ-ACK within a Sub-slot | Ericsson |
| R1-2111216 | Discussion on overlapping between CG PUSCH and DG PUSCH | CATT |
| R1-2111217 | Correction on UL cancellation | CATT |
| R1-2111218 | Discussion on intra-UE multiplexing/prioritization for eURLLC | CATT |
| R1-2111336 | Discussion and draft CR on UE PDSCH processing time for DCI format 1_2 | OPPO |
| R1-2111337 | Discussion and draft CR on scheduling and HARQ enhancement | OPPO |
| R1-2111338 | Remaining issues on intra-UE prioritization or multiplexing | OPPO |
| R1-2111362 | Draft CR on UL multiplexing with SPS HARQ-ACK or SR in one sub-slot | ZTE |
| R1-2111679 | [Draft CR] Clarification on Inter-sub-slot multiplexing of low-priority UCIs | Nokia, Nokia Shanghai Bell |
| R1-2111680 | Correction on UE procedure for intra-UE prioritization/multiplexing | Nokia, Nokia Shanghai Bell |
| R1-2111682 | Rel-16 URLLC/IIoT PUSCH skipping (with LCH and/or PHY prioritization configured) | Nokia, Nokia Shanghai Bell |
| R1-2111849 | UCI multiplexing and UL skipping in Rel-16 URLLC | Apple |
| R1-2111850 | Remaining issues on intra-UE multiplexing/prioritization for eURLLC | Apple |
| R1-2112170 | Correction on RRC parameter name of Type-1 HARQ-ACK codebook in TS 38.213 | ITRI |
| R1-2112194 | Remaining issues on eCG enhancements for URLLC | Qualcomm Incorporated |
| R1-2112398 | Resolving Overlapping SPS HARQ-ACK with Repetition | Ericsson |
| R1-2112408 | Corrections on RRC signaling for scaling PDCCH monitoring capability for NR-DC operation | Huawei, HiSilicon |
| R1-2112478 | Summary of preparation phase email discussion for Rel-16 eURLLC | Moderator (Huawei) |
| R1-2112697 | Summary of [107-e-NR-L1enh-URLLC-03] Discussion on issues related to SRS resource sets configured for DCI format 0_1 and DCI format 0_2 | Moderator (vivo) |
| R1-2112725 | Draft reply LS on PDCCH Blind Detection in CA | Huawei |
| R1-2112726 | Summary of email discussion [107-e-NR-L1enh-URLLC-01] Discussion on LS from RAN2 on blind detection in CA | Moderator (Huawei) |
| R1-2112727 | Summary of email discussion [107-e-NR-L1enh-URLLC-08] Miscellaneous corrections on Rel-16 URLLC | Moderator (Huawei) |
| R1-2112736 | Clarification on intra-UE prioritization/multiplexing on semi-static symbols | Moderator (CATT), Nokia, Nokia Shanghai Bell, Huawei, HiSilicon |
| R1-2112737 | Summary of [107-e-NR-L1enh-URLLC-07] Discussion on correction on UL cancellation | Moderator (CATT) |
| R1-2112748 | Summary of [107-e-NR-L1enh-URLLC-04] Discussion on remaining issues on UL prioritization and UL skipping | Moderator (vivo) |
| R1-2112749 | [Draft] Reply LS on UL skipping with LCH prioritization | Moderator (vivo) |
| R1-2112759 | Summary of [107-e-NR-L1enh-URLLC-06] Discussion on PUCCH multiplexing with SPS HARQ-ACK within a sub-slot | Moderator (Nokia) |
| R1-2112807 | Summary of email discussion [107-e-NR-L1enh-URLLC-02] Discussion on PDSCH processing timeline for DCI format 1_2 | Moderator (Ericsson) |
| R1-2112808 | Corrections on UE PDSCH processing time for DCI format 1_2 | Moderator (Ericsson), Intel |
| R1-2112833 | Reply LS on PDCCH Blind Detection in CA | RAN1, Huawei |
| R1-2112861 | PUCCH multiplexing with SPS HARQ-ACK or SR within a sub-slot | Moderator (Nokia), Nokia Shanghai Bell, ZTE, Qualcomm, Huawei, HiSilicon, Ericsson |
| R1-2112862 | Reply LS on UL skipping with LCH prioritization | RAN1, vivo |
| R1-2112889 | Summary of email discussion [107-e-NR-L1enh-URLLC-05] on UCI multiplexing and prioritization in Rel-16 | Moderator (Apple) |
| 7.2.6 | Maintenance of Enhancements on MIMO for NR | |
| R1-2110966 | Draft CR on gNB response for SCell-BFR | ZTE |
| R1-2110967 | Draft CR on SCS determination of 28 symbols for Rel-16 SCell BFR | ZTE |
| R1-2111219 | Draft CR on MU-CSI enhancement | CATT |
| R1-2111672 | Clarification on DCI 1_2 antenna port determination in TS 38.212 | Ericsson |
| R1-2111713 | Correction on frequency granularity of CSI based on Rel.16 Type II codebooks | Samsung |
| R1-2111851 | Draft CR on SCell candidate beam detection | Apple |
| R1-2111852 | Draft CR on SRS transmission for uplink full power | Apple |
| R1-2112195 | Discussion on UCI issues for eType II CSI | Qualcomm Incorporated |
| R1-2112355 | Corrections on eType II codebook tables | Nokia |
| R1-2112399 | Correction on the description of MAC-CE application time in TS 38.214 | Huawei, HiSilicon |
| R1-2112412 | Correction of UCI mapping for eType II codebook | Huawei, HiSilicon |
| R1-2112537 | Summary for Rel.16 NR eMIMO maintenance | Moderator (Samsung) |
| R1-2112597 | Summary of email thread [107-e-NR-eMIMO-02] | Moderator (Apple Inc.) |
| R1-2112598 | Outcome of email thread [107-e-NR-eMIMO-02] | Moderator (Apple Inc.) |
| R1-2112621 | Email Discussion Summary of [107-e-NR-eMIMO-01] | Moderator (ZTE) |
| R1-2112863 | Email Discussion Summary of [107-e-NR-eMIMO-03] | Moderator (Qualcomm) |
| R1-2112864 | Clarification on KNZ to codepoint mapping for eType II CSI | Moderator (Qualcomm Incorporated), Huawei, HiSilicon |
| 7.2.7 | Maintenance of UE Power Saving for NR | |
| R1-2112264 | Remaining issues for Power Saving | Qualcomm Incorporated |
| R1-2112375 | Missed editorial on cross-slot scheduling based power saving | Nokia, Nokia Shanghai Bell |
| R1-2112410 | Maintenance on Rel-16 UE Power Saving | Huawei, HiSilicon |
| R1-2112559 | Preparation Summary of UE Power Saving | Moderator (CATT) |
| R1-2112825 | Session notes for 7.2.7 (Maintenance of UE Power Saving for NR) | Ad-Hoc Chair (CMCC) |
| 7.2.8 | Maintenance of NR positioning support | |
| R1-2110847 | Correction to PRS QCL Type D | Huawei, HiSilicon |
| R1-2110848 | Correction to the time stamp | Huawei, HiSilicon |
| R1-2110968 | Draft CR on QCL information for a DL PRS resource | ZTE |
| R1-2110989 | Maintenance on Rel-16 NR positioning | vivo |
| R1-2111220 | Draft CR on the parameter NR-TimeStamp for Rel-16 Positioning | CATT |
| R1-2112265 | Remaining issues for Positioning | Qualcomm Incorporated |
| R1-2112337 | Maintenance for NR positioning support | Ericsson |
| R1-2112415 | Draft CR on PRS processing | Nokia, Nokia Shanghai Bell |
| R1-2112560 | Summary of [107-e-NR-Pos-04] | Moderator (vivo) |
| R1-2112565 | Summary of the preparation phase for Rel.16 NR positioning maintenance | Moderator (Intel Corporation) |
| R1-2112661 | Summary of email discussion for [107-e-NR-Pos-03] | Moderator (ZTE Corporation) |
| R1-2112665 | Summary on email discussion [107-e-NR-Pos-05] for the UE report of parameter NR-TimeStamp | Moderator (CATT) |
| R1-2112698 | Summary #1 of [107-e-NR-Pos-01] Correction to PRS QCL Type D | Moderator (Huawei) |
| R1-2112699 | Summary #1 of [107-e-NR-Pos-02] Correction to the time stamp | Moderator (Huawei) |
| R1-2112788 | Session notes for 7.2.8 (Maintenance of NR positioning support) | Ad-Hoc Chair (Huawei) |
| 7.2.9 | Maintenance of NR Mobility Enhancements | |
| R1-2112266 | Remaining issues for Mobility Enhancement | Qualcomm Incorporated |
| 7.2.10 | Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements (LTE, NR) | |
| R1-2111934 | Discussion on case-1 dormancy operation with data scheduling | Huawei, HiSilicon |
| R1-2112575 | [107-e-Prep-AI7.2.10] Preparation phase for Rel-16 NR MR-DC & CA maintenance Email discussion summary | Moderator (Nokia) |
| R1-2112692 | Correction on Case 1 dormancy operation with data scheduling | Moderator (Huawei), HiSilicon |
| R1-2112693 | Discussion on dormancy indication Case-1 | Moderator (Huawei) |
| R1-2112789 | Session notes for 7.2.10 (Maintenance of Multi-RAT Dual-Connectivity and Carrier Aggregation enhancements) | Ad-Hoc Chair (Huawei) |
| 7.2.11 | NR Rel-16 UE Features | |
| R1-2111168 | On UE features for PDCCH Blind Detection in CA | Nokia, Nokia Shanghai Bell |
| R1-2111935 | UE PRS processing capability correction | Huawei, HiSilicon |
| R1-2112463 | Summary on Rel-16 NR UE features related discussion | Moderator (NTT DOCOMO, INC.) |
| R1-2112538 | Summary on [107-e-AI7.2.11-NR-UEFeature-Positioning-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2112539 | Summary on [107-e-AI7.2.11-NR-UEFeature-Others-01] | Moderator (NTT DOCOMO, INC.) |
| R1-2112777 | Updated RAN1 UE features list for Rel-16 NR after RAN1#107-e | Moderator (NTT DOCOMO, INC.) |
| R1-2112778 | LS on updated Rel-16 RAN1 UE features lists for NR after RAN1#107-e | RAN1, NTT DOCOMO |
| 7.2.12 | Other | |
| R1-2111933 | Discussion on the remaining problems of supporting Tx switching between two uplink carriers | Huawei, HiSilicon |
| R1-2112275 | Summary of Rel-16 uplink Tx switching | Moderator (China Telecom) |
| 8 | Release 17 | |
| R1-2111193 | Recommendations for RAN1 RRC Parameter Preparation | Moderator (Ericsson) |
| R1-2112839 | [DRAFT] LS on Re-17 MAC-CE impacts | Nokia |
| R1-2112840 | Rel-17 WI impacts on MAC Control Elements | Moderator (Nokia) |
| R1-2112841 | [107-e-R18-MAC-CE] Email discussion summary | Moderator (Nokia) |
| R1-2112842 | LS on Re-17 MAC-CE impacts | RAN1, Nokia |
| R1-2112974 | DRAFT LS on updated Rel-17 LTE and NR higher-layers parameter list | Moderator (Ericsson) |
| R1-2112975 | Consolidated higher layers parameter list for Rel-17 LTE | Moderator (Ericsson) |
| R1-2112976 | Consolidated higher layers parameter list for Rel-17 NR | Moderator (Ericsson) |
| R1-2112977 | LS on updated Rel-17 LTE and NR higher-layers parameter list | RAN1, Ericsson |
| R1-2112978 | Summary of Email discussion on Rel-17 RRC parameters for LS to RAN2 | Moderator (Ericsson) |
| R1-2112979 | Collection of updated higher layers parameter list for Rel-17 LTE and NR | Moderator (Ericsson) |
| 8.1 | Further enhancements on MIMO for NR | |
| R1-2112430 | Introduction of MIMO enhancements | Ericsson |
| R1-2112446 | Introduction of further enhancements on MIMO for NR | Samsung |
| R1-2112472 | Introduction of Further enhancements on MIMO for NR | Huawei |
| R1-2112483 | Introduction of further enhancements on MIMO for NR | Nokia |
| R1-2112764 | Moderator summary for Rel-17 NR_FeMIMO RRC parameters | Moderator (Samsung) |
| R1-2112919 | Introduction of MIMO enhancements | Ericsson |
| R1-2112941 | Introduction of Further enhancements on MIMO for NR | Huawei |
| R1-2112949 | Introduction of further enhancements on MIMO for NR | Nokia |
| R1-2112986 | Introduction of further enhancements on MIMO for NR | Samsung |
| 8.1.1 | Enhancements on Multi-beam Operation | |
| R1-2110761 | Remaining Issues for Multi-beam Operation | InterDigital, Inc. |
| R1-2110781 | Enhancements on multi-beam operation in Rel-17 | Huawei, HiSilicon |
| R1-2110883 | Enhancement on multi-beam operation | FUTUREWEI |
| R1-2110932 | Enhancements on Multi-beam Operation | Lenovo, Motorola Mobility |
| R1-2110948 | Enhancements on Multi-beam Operation | ZTE |
| R1-2110990 | Remaining issues on multi beam enhancement | vivo |
| R1-2111084 | Enhancements on Multi-beam Operation | Spreadtrum Communications |
| R1-2111143 | Enhancements on Multi-beam Operation | Fujitsu |
| R1-2111169 | Enhancements on multi-beam operation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2111221 | Remaining issues on Rel-17 multi-beam operation | CATT |
| R1-2111279 | Enhancements on Multi-beam Operation | OPPO |
| R1-2111380 | Further enhancement on multi-beam operation | Sony |
| R1-2111453 | Enhancements on Multi-beam Operation | LG Electronics |
| R1-2111476 | Enhancements to Multi-Beam Operations | Intel Corporation |
| R1-2111540 | Enhancements on multi-beam operation | Xiaomi |
| R1-2111597 | Enhancements on multi-beam operation | CMCC |
| R1-2111683 | Discussion on remaining issues on multi-beam operation | NEC |
| R1-2111715 | Moderator summary for multi-beam enhancement | Moderator (Samsung) |
| R1-2111716 | Summary of offline discussion on unified TCI, inter-cell beam management, and MPUE | Moderator (Samsung) |
| R1-2111717 | Multi-Beam Enhancements | Samsung |
| R1-2111786 | Remaining issues on multi-beam enhancements | Ericsson |
| R1-2111803 | Enhancements on Multi-Beam Operations | AT&T |
| R1-2111853 | Views on Rel-17 Beam Management enhancement | Apple |
| R1-2112008 | Enhancements on Multi-beam Operation | Convida Wireless |
| R1-2112087 | Enhancements on multi-beam operation | TCL Communication Ltd. |
| R1-2112089 | Discussion on multi-beam operation | NTT DOCOMO, INC. |
| R1-2112176 | Enhancements on Multi-beam Operation | Nokia, Nokia Shanghai Bell |
| R1-2112196 | Enhancements on Multi-beam Operation | Qualcomm Incorporated |
| R1-2112276 | Enhancement on multi-beam operation | MediaTek Inc. |
| R1-2112581 | Moderator summary#2 for multi-beam enhancement: ROUND 1 | Moderator (Samsung) |
| R1-2112680 | Moderator summary#3 for multi-beam enhancement: ROUND 2 | Moderator (Samsung) |
| R1-2112707 | Follow-up reply LS on inter-cell beam management and multi-TRP in Rel-17 | RAN1, Huawei |
| R1-2112762 | LS on L1-RSRP measurement behavior when SSBs associated with different PCIs overlap | RAN1, vivo |
| R1-2112763 | Moderator summary#4 for multi-beam enhancement: ROUND 3 | Moderator (Samsung) |
| 8.1.2.1 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | |
| R1-2110762 | Further Discussion on Enhancements for PDCCH, PUCCH, and PUSCH | InterDigital, Inc. |
| R1-2110782 | Enhancements on multi-TRP for reliability and robustness in Rel-17 | Huawei, HiSilicon |
| R1-2110879 | Multi-TRP/panel for non-PDSCH | FUTUREWEI |
| R1-2110933 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Lenovo, Motorola Mobility |
| R1-2110949 | Multi-TRP enhancements for PDCCH, PUCCH and PUSCH | ZTE |
| R1-2110991 | Remaining issues on Multi-TRP for PDCCH, PUCCH and PUSCH enhancements | vivo |
| R1-2111085 | Discussion on enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Spreadtrum Communications |
| R1-2111144 | Enhancements on Multi-TRP for PDCCH PUCCH and PUSCH | Fujitsu |
| R1-2111170 | On multi-TRP enhancements for PDCCH | Fraunhofer IIS, Fraunhofer HHI |
| R1-2111222 | Remaining issues on multi-TRP/panel for PDCCH, PUCCH and PUSCH | CATT |
| R1-2111280 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | OPPO |
| R1-2111381 | Considerations on Multi-TRP for PDCCH, PUCCH, PUSCH | Sony |
| R1-2111454 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | LG Electronics |
| R1-2111477 | Multi-TRP enhancements for PDCCH, PUCCH and PUSCH | Intel Corporation |
| R1-2111541 | Enhancements on Multi-TRP for PDCCH, PUSCH and PUCCH | Xiaomi |
| R1-2111598 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | CMCC |
| R1-2111684 | Discussion on multi-TRP for PDCCH, PUCCH and PUSCH | NEC |
| R1-2111718 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Samsung |
| R1-2111854 | Views on Rel-17 multi-TRP reliability enhancement | Apple |
| R1-2112026 | Multi-TRP Enhancements for PDCCH | Convida Wireless |
| R1-2112074 | Discussion on enhancements on multi-TRP for uplink channels | FGI, Asia Pacific Telecom |
| R1-2112090 | Discussion on MTRP for reliability | NTT DOCOMO, INC. |
| R1-2112177 | Enhancements for Multi-TRP URLLC schemes | Nokia, Nokia Shanghai Bell |
| R1-2112197 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | Qualcomm Incorporated |
| R1-2112269 | Discussion on mTRP PUSCH | ASUSTeK |
| R1-2112271 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | TCL Communication Ltd. |
| R1-2112277 | Enhancements on Multi-TRP for PDCCH, PUCCH and PUSCH | MediaTek Inc. |
| R1-2112320 | Remaining issues on PDCCH, PUSCH and PUCCH enhancements for multi-TRP | Ericsson |
| R1-2112453 | Summary #1 of [107-e-NR-feMIMO-02] Email discussion on multi-TRP for PDCCH | Moderator (Qualcomm) |
| R1-2112454 | Summary #2 of [107-e-NR-feMIMO-02] Email discussion on multi-TRP for PDCCH | Moderator (Qualcomm) |
| R1-2112455 | Summary #3 of [107-e-NR-feMIMO-02] Email discussion on multi-TRP for PDCCH | Moderator (Qualcomm) |
| R1-2112583 | Summary #1 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| R1-2112584 | Summary #2 of Multi-TRP for PUCCH and PUSCH | Moderator (Nokia) |
| 8.1.2.2 | Enhancements on Multi-TRP inter-cell operation | |
| R1-2110763 | Details on M-TRP Inter-cell Operation | InterDigital, Inc. |
| R1-2110783 | Enhancements on inter-cell multi-TRP operation in Rel-17 | Huawei, HiSilicon |
| R1-2110880 | Inter-cell multi-TRP operation | FUTUREWEI |
| R1-2110934 | Enhancements on Multi-TRP inter-cell operation | Lenovo, Motorola Mobility |
| R1-2110946 | Finalizing Multi-TRP inter-cell operation | Ericsson |
| R1-2110950 | Discussion on Multi-TRP inter-cell operation | ZTE |
| R1-2110992 | Remaining issues on inter-cell MTRP operation | vivo |
| R1-2111086 | Discussion on enhancements on multi-TRP inter-cell operation | Spreadtrum Communications |
| R1-2111223 | Remaining issues on inter-cell operation for multi-TRP/panel | CATT |
| R1-2111281 | Enhancement on inter-cell multi-TRP operation | OPPO |
| R1-2111455 | Enhancements on Multi-TRP inter-cell operation | LG Electronics |
| R1-2111478 | Multi-TRP enhancements for inter-cell operation | Intel Corporation |
| R1-2111542 | Discussion on Multi-TRP Inter-cell operation | Xiaomi |
| R1-2111599 | Enhancements on Multi-TRP inter-cell operation | CMCC |
| R1-2111685 | Discussion on multi-TRP inter-cell operation | NEC |
| R1-2111719 | Enhancements on Multi-TRP inter-cell operation | Samsung |
| R1-2111855 | Views on Rel-17 Inter-cell multi-TRP operation | Apple |
| R1-2112078 | Discussion on Multi-TRP inter-cell operation | ASUSTEK |
| R1-2112091 | Discussion on inter-cell multi-TRP operation | NTT DOCOMO, INC. |
| R1-2112178 | Enhancements to enable inter-cell multi-TRP operations | Nokia, Nokia Shanghai Bell |
| R1-2112198 | Enhancements on Multi-TRP inter-cell operation | Qualcomm Incorporated |
| R1-2112816 | Feature lead summary on Enhancements on Multi-TRP inter-cell operation | Moderator (vivo) |
| 8.1.2.3 | Enhancements on beam management for multi-TRP | |
| R1-2110764 | Further Discussion on Beam Management Enhancements for Multi-TRP | InterDigital, Inc. |
| R1-2110784 | Enhancements on beam management for multi-TRP in Rel-17 | Huawei, HiSilicon |
| R1-2110881 | Beam management for simultaneous multi-TRP transmission with multi-panel reception | FUTUREWEI |
| R1-2110935 | Enhancements on beam management for multi-TRP | Lenovo, Motorola Mobility |
| R1-2110951 | Enhancements on beam management for Multi-TRP | ZTE |
| R1-2110993 | Remaining issues on MTRP multibeam enhancement | vivo |
| R1-2111087 | Discussion on enhancements on beam management for multi-TRP | Spreadtrum Communications |
| R1-2111145 | Enhancements on beam management for multi-TRP | Fujitsu |
| R1-2111224 | Remaining issues on beam management for multi-TRP | CATT |
| R1-2111282 | Enhancements on beam management for multi-TRP | OPPO |
| R1-2111382 | Enhancements on beam management for multi-TRP | Sony |
| R1-2111456 | Enhancements on beam management for multi-TRP | LG Electronics |
| R1-2111479 | Multi-TRP enhancements for beam management | Intel Corporation |
| R1-2111543 | Enhancements on beam management for Multi-TRP | Xiaomi |
| R1-2111600 | Enhancements on beam management for multi-TRP | CMCC |
| R1-2111686 | Discussion on beam management for multi-TRP | NEC |
| R1-2111720 | Enhancements on beam management for multi-TRP | Samsung |
| R1-2111856 | Views on Rel-17 multi-TRP BM enhancement | Apple |
| R1-2111986 | Enhancements on beam management for multi-TRP | ETRI |
| R1-2112027 | On Multi-TRP BFR | Convida Wireless |
| R1-2112077 | Discussion of enhancements on beam management for multi-TRP | FGI, Asia Pacific Telecom |
| R1-2112092 | Discussion on beam management for MTRP | NTT DOCOMO, INC. |
| R1-2112171 | Discussion on beam management for multi-TRP | ITRI |
| R1-2112179 | Enhancements on Beam Management for Multi-TRP/Panel Transmission | Nokia, Nokia Shanghai Bell |
| R1-2112199 | Enhancements on beam management for multi-TRP | Qualcomm Incorporated |
| R1-2112274 | Enhancements on beam management for multi-TRP | TCL Communication Ltd. |
| R1-2112278 | Enhancement on beam management for multi-TRP | MediaTek Inc. |
| R1-2112321 | Remaining issues on beam management for multi-TRP | Ericsson |
| R1-2112613 | Summary of enhancements on beam management for multi-TRP (Round 1) | Moderator (CATT) |
| R1-2112644 | Summary of enhancements on beam management for multi-TRP (Round 2) | Moderator (CATT) |
| 8.1.2.4 | Enhancements on HST-SFN deployment | |
| R1-2110765 | On M-TRP Operation for HST-SFN Deployment | InterDigital, Inc. |
| R1-2110785 | Enhancements on HST multi-TRP deployment in Rel-17 | Huawei, HiSilicon |
| R1-2110952 | Discussion on Multi-TRP HST enhancements | ZTE |
| R1-2110994 | Remaining issues on HST-SFN schemes | vivo |
| R1-2111088 | Discussion on enhancements on HST-SFN deployment | Spreadtrum Communications |
| R1-2111225 | Remaining issues on HST-SFN deployment | CATT |
| R1-2111283 | Enhancements on HST-SFN deployment | OPPO |
| R1-2111383 | Enhancements HST-SFN deployment | Sony |
| R1-2111457 | Enhancements on HST-SFN deployment | LG Electronics |
| R1-2111480 | Enhancements to HST-SFN deployments | Intel Corporation |
| R1-2111544 | Enhancements on HST-SFN deployment | Xiaomi |
| R1-2111601 | Enhancements on HST-SFN deployment | CMCC |
| R1-2111668 | Remaining issues on HST-SFN enhancements | Ericsson |
| R1-2111687 | Discussion on HST-SFN deployment | NEC |
| R1-2111721 | Enhancements on HST-SFN | Samsung |
| R1-2111857 | Views on Rel-17 HST enhancement | Apple |
| R1-2111940 | Enhancements for HST-SFN deployment | Lenovo, Motorola Mobility |
| R1-2112028 | On Enhancements for HST-SFN deployment | Convida Wireless |
| R1-2112093 | Discussion on HST-SFN deployment | NTT DOCOMO, INC. |
| R1-2112180 | Enhancements for HST-SFN deployment | Nokia, Nokia Shanghai Bell |
| R1-2112200 | Enhancements on HST-SFN deployment | Qualcomm Incorporated |
| R1-2112279 | Enhancements on HST-SFN deployment | MediaTek Inc. |
| R1-2112588 | Summary#1 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2112660 | Summary#2 of AI: 8.1.2.4 Enhancements on HST-SFN deployment | Moderator (Intel Corporation) |
| R1-2112829 | LS on BFR for CORESET with two activated TCI states | RAN1, ZTE |
| 8.1.3 | Enhancements on SRS flexibility, coverage and capacity | |
| R1-2110766 | Remaining Details on SRS Enhancements | InterDigital, Inc. |
| R1-2110786 | Enhancements on SRS in Rel-17 | Huawei, HiSilicon |
| R1-2110882 | Enhancements on SRS flexibility, coverage and capacity | FUTUREWEI |
| R1-2110936 | Enhancements on SRS | Lenovo, Motorola Mobility |
| R1-2110947 | Finalizing SRS | Ericsson |
| R1-2110953 | Enhancements on SRS flexibility, coverage and capacity | ZTE |
| R1-2110964 | FL summary #1 on SRS enhancements | Moderator (ZTE) |
| R1-2110995 | Remaining issues on SRS enhancement | vivo |
| R1-2111089 | Considerations on SRS enhancements | Spreadtrum Communications |
| R1-2111226 | Remaining issues on SRS enhancement | CATT |
| R1-2111284 | Enhancements on SRS flexibility, coverage and capacity | OPPO |
| R1-2111458 | Enhancements on SRS flexibility, coverage and capacity | LG Electronics |
| R1-2111481 | Discussion on SRS enhancements | Intel Corporation |
| R1-2111545 | Discussion on SRS enhancements | Xiaomi |
| R1-2111602 | Enhancements on SRS flexibility, coverage and capacity | CMCC |
| R1-2111688 | Discussion on SRS enhancement | NEC |
| R1-2111722 | Enhancements on SRS | Samsung |
| R1-2111858 | Views on Rel-17 SRS enhancement | Apple |
| R1-2112094 | Discussion on SRS enhancement | NTT DOCOMO, INC. |
| R1-2112181 | Enhancements on SRS flexibility, coverage and capacity | Nokia, Nokia Shanghai Bell |
| R1-2112201 | Enhancements on SRS flexibility, coverage and capacity | Qualcomm Incorporated |
| R1-2112280 | Enhancements on SRS flexibility, coverage and capacity | MediaTek Inc. |
| R1-2112589 | FL summary #2 on SRS enhancements | Moderator (ZTE) |
| 8.1.4 | CSI enhancements: MTRP and FR1 FDD reciprocity | |
| R1-2110767 | Remaining Details on CSI Enhancements for NCJT MTRP | InterDigital, Inc. |
| R1-2110787 | CSI enhancements on MTRP and FDD in Rel-17 | Huawei, HiSilicon |
| R1-2110954 | CSI enhancements for Multi-TRP and FR1 FDD reciprocity | ZTE |
| R1-2110996 | Remaining issues on MTRP CSI and Partial reciprocity | vivo |
| R1-2111090 | Discussion on CSI enhancements for M-TRP and FR1 FDD reciprocity | Spreadtrum Communications |
| R1-2111171 | CSI enhancements on Type II PS codebook and multi-TRP | Fraunhofer IIS, Fraunhofer HHI |
| R1-2111227 | Remaining issues on CSI enhancement | CATT |
| R1-2111285 | CSI enhancement for M-TRP and FDD reciprocity | OPPO |
| R1-2111384 | Views on CSI enhancements | Sony |
| R1-2111459 | CSI enhancements for Rel-17 | LG Electronics |
| R1-2111482 | Remaining issues on CSI for MTRP and FDD | Intel Corporation |
| R1-2111603 | Enhancements on CSI reporting for Multi-TRP | CMCC |
| R1-2111689 | Discussion on CSI enhancement for multi-TRP | NEC |
| R1-2111723 | Views on Rel. 17 CSI enhancements | Samsung |
| R1-2111859 | Views on Rel-17 CSI enhancement | Apple |
| R1-2111941 | CSI enhancements for multi-TRP and FDD reciprocity | Lenovo, Motorola Mobility |
| R1-2112095 | Discussion on CSI enhancements | NTT DOCOMO, INC. |
| R1-2112182 | Enhancement on CSI measurement and reporting | Nokia, Nokia Shanghai Bell |
| R1-2112202 | CSI enhancements: MTRP and FR1 FDD reciprocity | Qualcomm Incorporated |
| R1-2112281 | CSI Enhancement for NCJT and FR1 FDD reciprocity | MediaTek Inc. |
| R1-2112322 | CSI enhancements for Multi-TRP and FR1 FDD reciprocity | Ericsson |
| R1-2112585 | Summary of CSI enhancements for MTRP and FDD (Round 0) | Moderator (Huawei, HiSilicon) |
| R1-2112586 | Summary of CSI enhancements for MTRP and FDD (Round 1) | Moderator (Huawei, HiSilicon) |
| R1-2112587 | Summary of CSI enhancements for MTRP and FDD (Round 2) | Moderator (Huawei, HiSilicon) |
| 8.1.5 | Other | |
| R1-2110768 | Views on Multi-Panel Multi-TRP MIMO | InterDigital, Inc. |
| R1-2110955 | Further details on Multi-beam and Multi-TRP operation | ZTE |
| R1-2110997 | Discussion on impact of cross-talk on UL performance | vivo |
| R1-2111175 | Our views on Rel-18 MIMO WI content | Ericsson |
| R1-2111724 | Additional enhancements for multi-beam | Samsung |
| R1-2111860 | On Further MIMO Enhancement | Apple |
| R1-2111918 | Further considerations for FeMIMO in Rel-17 | Huawei, HiSilicon |
| 8.2 | Supporting NR from 52.6GHz to 71 GHz | |
| R1-2112425 | Introduction of NR extensions to 71 GHz | Intel Corporation |
| R1-2112428 | Introduction of features to extend current NR operation to 71 GHz | Ericsson |
| R1-2112431 | Introduction of extensions to 71 GHz | Ericsson |
| R1-2112443 | Introduction for extending NR operation to 71 GHz | Samsung |
| R1-2112468 | Introduction of features to extend current NR operation to 71 GHz | Huawei |
| R1-2112482 | Introduction of NR Extending current NR operation to 71GHz | Nokia |
| R1-2112773 | Email discussion summary for RRC parameters for 52.6-71GHz | Moderator (Qualcomm Incorporated) |
| R1-2112790 | Session notes for 8.2 (Extending current NR operation to 71GHz) | Ad-Hoc Chair (Huawei) |
| R1-2112914 | Introduction of NR extensions to 71 GHz | Intel Corporation |
| R1-2112917 | Introduction of features to extend current NR operation to 71 GHz | Ericsson |
| R1-2112920 | Introduction of extensions to 71 GHz | Ericsson |
| R1-2112931 | Introduction for extending NR operation to 71 GHz | Samsung |
| R1-2112937 | Introduction of features to extend current NR operation to 71 GHz | Huawei |
| R1-2112948 | Introduction of NR Extending current NR operation to 71GHz | Nokia |
| 8.2.1 | Initial access aspects | |
| R1-2110827 | Initial access signals and channels for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2110872 | Initial access for Beyond 52.6GHz | FUTUREWEI |
| R1-2110998 | Remaining issues on initial access aspects for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2111074 | Discussion on the initial access aspects for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2111091 | Discussion on initial access aspects for NR for 60GHz | Spreadtrum Communications |
| R1-2111146 | Considerations on initial access for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2111195 | Initial access aspects | Nokia, Nokia Shanghai Bell |
| R1-2111241 | Initial access aspects for up to 71GHz operation | CATT |
| R1-2111307 | Discussion on initial access aspects | OPPO |
| R1-2111385 | Considerations on initial access aspects for NR from 52.6 GHz to 71 GHz | Sony |
| R1-2111463 | Initial Access Aspects | Ericsson |
| R1-2111483 | Discussion on initial access aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2111641 | Initial access aspects for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2111701 | Discussion on initial access aspects supporting NR from 52.6 to 71 GHz | NEC |
| R1-2111725 | Initial access aspects for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2111788 | Initial access aspects for NR from 52.6 GHz to 71 GHz | Panasonic Corporation |
| R1-2111832 | Discussion on initial access channels and signals for operation in 52.6-71GHz | InterDigital, Inc. |
| R1-2111861 | Initial access signals and channels | Apple |
| R1-2111987 | Discussion on initial access aspects for NR from 52.6 to 71GHz | ETRI |
| R1-2112011 | Initial access aspects | Sharp |
| R1-2112029 | NR SSB design consideration for 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2112045 | Initial access aspects to support NR above 52.6 GHz | LG Electronics |
| R1-2112096 | Initial access aspects for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2112203 | Initial access aspects for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2112290 | Remaining issues on initial access of 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2112384 | Remaining issues on initial access aspects for NR beyond 52.6GHz | WILUS Inc. |
| R1-2112450 | Issue Summary for initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2112451 | Summary #1 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2112452 | Summary #2 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2112580 | Issue Summary for initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2112614 | [Draft] LS on initial access for 60 GHz | Intel Corporation |
| R1-2112734 | [Draft] LS on RA-RNTI and MSGB-RNTI for 480 and 960 kHz | Intel Corporation |
| R1-2112735 | Summary #3 of email discussion on initial access aspect of NR extension up to 71 GHz | Moderator (Intel Corporation) |
| R1-2112805 | LS on initial access for 60 GHz | RAN1, Intel Corporation |
| R1-2112832 | LS on RA-RNTI and MSGB-RNTI for 480 and 960 kHz | RAN1, Intel Corporation |
| 8.2.2 | PDCCH monitoring enhancements | |
| R1-2110828 | Enhancement on PDCCH monitoring | Huawei, HiSilicon |
| R1-2110873 | PDCCH monitoring enhancements for Beyond 52.6GHz | FUTUREWEI |
| R1-2110999 | Remaining issues on PDCCH monitoring enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2111075 | Discussion on the PDCCH monitoring enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2111092 | Discussion on the PDCCH monitoring enhancements for above 52.6GHz | Spreadtrum Communications |
| R1-2111196 | PDCCH monitoring enhancements | Nokia, Nokia Shanghai Bell |
| R1-2111242 | PDCCH monitoring enhancements for up to 71GHz operation | CATT |
| R1-2111308 | Discussion on PDCCH monitoring enhancement | OPPO |
| R1-2111386 | PDCCH enhancement for NR from 52.6GHz to 71GHz | Sony |
| R1-2111419 | PDCCH monitoring enhancements | Charter Communications |
| R1-2111464 | PDCCH Monitoring Enhancements | Ericsson |
| R1-2111484 | Discussion on PDCCH monitoring enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2111563 | PDCCH monitoring enhancement for NR 52.6-71GHz | Xiaomi |
| R1-2111642 | PDCCH monitoring enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2111673 | Discussion on PDCCH monitoring enhancements for above 52.6GHz | Transsion Holdings |
| R1-2111691 | Discussion on PDCCH monitoring enhancements supporting NR from 52.6GHz to 71 GHz | NEC |
| R1-2111708 | PDCCH monitoring for NR operation from 52.6 to 71 GHz | Panasonic |
| R1-2111726 | PDCCH monitoring enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2111833 | Discussions on PDCCH monitoring enhancements | InterDigital, Inc. |
| R1-2111862 | Discussion on PDCCH Enhancements | Apple |
| R1-2112012 | PDCCH monitoring enhancements | Sharp |
| R1-2112030 | PDCCH Monitoring enhancement for NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2112046 | PDCCH monitoring enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2112097 | PDCCH monitoring enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2112204 | PDCCH monitoring enhancements for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2112301 | PDCCH monitoring enhancement for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2112414 | Feature lead summary #1 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2112626 | Feature lead summary #2 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2112627 | Feature lead summary #3 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| R1-2112755 | Feature lead summary #4 for B52.6 GHz PDCCH monitoring enhancements | Moderator (Lenovo) |
| 8.2.3 | Enhancements for PUCCH formats 0/1/4 | |
| R1-2110829 | Enhancement on PUCCH formats | Huawei, HiSilicon |
| R1-2110874 | Discussion on Enhancements of PUCCH formats for Beyond 52.6GHz | FUTUREWEI |
| R1-2111000 | Remaining issues on PUCCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2111076 | Discussion on the PUCCH enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2111197 | Remaining items for enhanced PUCCH formats 0/1/4 | Nokia, Nokia Shanghai Bell |
| R1-2111243 | Enhancements for PUCCH formats for up to 71GHz operation | CATT |
| R1-2111309 | Discussion on enhancements for PUCCH format 0/1/4 | OPPO |
| R1-2111387 | Views on enhancements for PUCCH formats 0/1/4 | Sony |
| R1-2111465 | PUCCH enhancements | Ericsson |
| R1-2111466 | FL Summary for Enhancements for PUCCH formats 0/1/4 | Moderator (Ericsson) |
| R1-2111485 | Discussion on PUCCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2111834 | Discussions on enhancements for PUCCH formats 0/1/4 | InterDigital, Inc. |
| R1-2111863 | Discussion on Enhancements for PUCCH formats 0_1_4 | Apple |
| R1-2112047 | Enhancements for PUCCH formats 0/1/4 to support NR above 52.6 GHz | LG Electronics |
| R1-2112098 | PUCCH format 0/1/4 enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2112205 | Enhancements for PUCCH for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| 8.2.4 | Beam management for new SCSs | |
| R1-2110830 | Discussion on the beam management procedures for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2110875 | Beam management for Beyond 52.6GHz | FUTUREWEI |
| R1-2111001 | Remaining issues on beam management for new SCSs for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2111077 | Discussion on the beam management for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2111198 | Beam Management Aspects | Nokia, Nokia Shanghai Bell |
| R1-2111244 | Beam management for new SCSs for up to 71GHz operation | CATT |
| R1-2111310 | Discussion on beam management for new SCSs | OPPO |
| R1-2111388 | Beam management enhancement for NR from 52.6GHz to 71GHz | Sony |
| R1-2111467 | Beam Management for New SCSs | Ericsson |
| R1-2111486 | Discussion on Beam management aspects for extending NR up to 71 GHz | Intel Corporation |
| R1-2111564 | Discussion on beam management for new SCSs | Xiaomi |
| R1-2111643 | Beam-management enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2111703 | Beam management enhancement for NR from 52.6GHz to 71GHz | NEC |
| R1-2111727 | Beam management for new SCSs for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2111835 | Discussions on beam management for new SCSs | InterDigital, Inc. |
| R1-2111836 | Discussion Summary #1 for Beam Management for new SCSs | Moderator (InterDigital, Inc.) |
| R1-2111864 | Beam Management for New SCSs | Apple |
| R1-2112031 | Beam management for NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2112048 | Enhancements for beam management to support NR above 52.6 GHz | LG Electronics |
| R1-2112099 | Beam based operation for new SCSs for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2112206 | Beam managment for new SCS | Qualcomm Incorporated |
| R1-2112302 | Beam management discussion for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2112623 | Discussion Summary #2 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| R1-2112624 | Discussion Summary #3 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| R1-2112814 | Discussion Summary #4 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| R1-2112815 | Discussion Summary #5 of Beam Management for New SCSs | Moderator (InterDigital, Inc.) |
| 8.2.5 | PDSCH/PUSCH enhancements | |
| R1-2110831 | PDSCH/PUSCH enhancements for 52-71GHz spectrum | Huawei, HiSilicon |
| R1-2110876 | Enhancements to support PDSCH/PUSCH for Beyond 52.6GHz | FUTUREWEI |
| R1-2111002 | Remaining issues on PDSCH/PUSCH enhancements for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2111078 | Discussion on the data channel enhancements for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2111147 | Considerations on multi-PDSCH/PUSCH with a single DCI and HARQ for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2111199 | PDSCH/PUSCH enhancements | Nokia, Nokia Shanghai Bell |
| R1-2111245 | PDSCH/PUSCH enhancements for up to 71GHz operation | CATT |
| R1-2111311 | Discussion on PDSCH/PUSCH enhancements | OPPO |
| R1-2111424 | Discussion on PDSCH/PUSCH enhancements for NR 52.6-71 GHz | Panasonic Corporation |
| R1-2111468 | PDSCH-PUSCH Enhancements | Ericsson |
| R1-2111487 | Discussion on PDSCH/PUSCH enhancements for extending NR up to 71 GHz | Intel Corporation |
| R1-2111565 | PDSCH and PUSCH enhancements for NR 52.6-71GHz | Xiaomi |
| R1-2111644 | PDSCH/PUSCH scheduling enhancements for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2111692 | Discussion on PDSCH enhancements supporting NR from 52.6GHz to 71 GHz | NEC |
| R1-2111728 | PDSCH/PUSCH enhancements for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2111837 | Enhancement for PDSCH/PUSCH to support 52.6 GHz-71 GHz band in NR | InterDigital, Inc. |
| R1-2111865 | Discussion on PDSCH and PUSCH Enhancements | Apple |
| R1-2112049 | PDSCH/PUSCH enhancements to support NR above 52.6 GHz | LG Electronics |
| R1-2112050 | Summary #1 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2112100 | PDSCH/PUSCH enhancements for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2112207 | PDSCH/PUSCH enhancements for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2112303 | Multi-PDSCH scheduling design for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2112522 | Summary of PDSCH/PUSCH enhancements (Bandwidth/Timeline/Reference signals) | Moderator (vivo) |
| R1-2112523 | Discussion summary #1 of [107-e-NR-52-71GHz-05] | Moderator (vivo) |
| R1-2112620 | Summary #2 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2112638 | [Draft] LS on the minimum time gap for wake-up and Scell dormancy indication for NR operation in 52.6 to 71 GHz | Moderator (vivo) |
| R1-2112639 | LS on the minimum time gap for wake-up and Scell dormancy indication for NR operation in 52.6 to 71 GHz | RAN1, vivo |
| R1-2112640 | Discussion summary #2 of [107-e-NR-52-71GHz-05] | Moderator (vivo) |
| R1-2112703 | Summary #3 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| R1-2112714 | Summary #4 of PDSCH/PUSCH enhancements (Scheduling/HARQ) | Moderator (LG Electronics) |
| 8.2.6 | Channel access mechanism | |
| R1-2110832 | Channel access mechanism for 60 GHz unlicensed operation | Huawei, HiSilicon |
| R1-2110877 | Channel access for Beyond 52.6GHz | FUTUREWEI |
| R1-2110894 | Discussion on relation between sensing beam and transmission beam | GDCNI |
| R1-2111003 | Remaining issues on channel access mechanism for NR operation from 52.6GHz to 71 GHz | vivo |
| R1-2111079 | Discussion on the channel access for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2111093 | Discussion on channel access mechanism for above 52.6GHz | Spreadtrum Communications |
| R1-2111148 | Considerations on channel access mechanism for NR from 52.6GHz to 71 GHz | Fujitsu |
| R1-2111200 | Channel access mechanism | Nokia, Nokia Shanghai Bell |
| R1-2111246 | Channel access mechanism for up to 71GHz operation | CATT |
| R1-2111312 | Discussion on channel access mechanism | OPPO |
| R1-2111389 | Channel access mechanism for 60 GHz unlicensed spectrum | Sony |
| R1-2111418 | Channel access mechanisms for NR above 52 GHz | Charter Communications |
| R1-2111469 | Channel Access Mechanisms | Ericsson |
| R1-2111488 | Discussion on channel access mechanism for extending NR up to 71 GHz | Intel Corporation |
| R1-2111566 | Discussion on channel access mechanism for NR on 52.6-71 GHz | Xiaomi |
| R1-2111645 | Channel access mechanisms for NR from 52.6 GHz to 71GHz | Lenovo, Motorola Mobility |
| R1-2111651 | Some discussions on channel access mechanism enhancements for 52.6-71 GHz | CAICT |
| R1-2111702 | Discussion on channel access mechanism supporting NR from 52.6 to 71GHz | NEC |
| R1-2111707 | Channel access for multi-beam operation | Panasonic |
| R1-2111729 | Channel access mechanism for NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2111838 | Discussion on channel access mechanisms | InterDigital, Inc. |
| R1-2111866 | Channel access mechanisms for unlicensed access above 52.6GHz | Apple |
| R1-2112032 | Channel Access Mechanism for Supporting NR from 52.6 GHz to 71 GHz | Convida Wireless |
| R1-2112051 | Channel access mechanism to support NR above 52.6 GHz | LG Electronics |
| R1-2112101 | Channel access mechanism for NR from 52.6 to 71 GHz | NTT DOCOMO, INC. |
| R1-2112166 | Remaining issue on channel access scheme for above 52.6GHz | ASUSTeK |
| R1-2112172 | Discussion on multi-beam operation | ITRI |
| R1-2112208 | Channel access mechanism for NR in 52.6 to 71GHz band | Qualcomm Incorporated |
| R1-2112268 | Channel access mechanism for NR in 60GHz unlicensed band operation | TCL Communication Ltd. |
| R1-2112291 | On the channel access mechanisms for 52.6-71 GHz NR operation | MediaTek Inc. |
| R1-2112385 | Remaining issues on channel access for NR from 52.6GHz to 71GHz | WILUS Inc. |
| R1-2112460 | Email discussion summary for channel access for beyond 52.6GHz band | Moderator (Qualcomm) |
| R1-2112617 | Email discussion summary#2 for channel access for beyond 52.6GHz band | Moderator (Qualcomm) |
| R1-2112690 | Email discussion summary#3 for channel access for beyond 52.6GHz band | Moderator (Qualcomm) |
| R1-2112706 | Draft LS to RAN4 on sensing beam selection | Qualcomm |
| R1-2112724 | Email discussion summary#4 for channel access for beyond 52.6GHz band | Moderator (Qualcomm) |
| R1-2112806 | LS on sensing beam selection | RAN1, Qualcomm |
| R1-2112820 | Email discussion summary#5 for channel access for beyond 52.6GHz band | Moderator (Qualcomm) |
| 8.2.7 | Other | |
| R1-2111004 | Remaining issues on CSI-RS related issues for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2111080 | Discussion on RRC parameters for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2111201 | PTRS enhancements for DFTsOFDM | Nokia, Nokia Shanghai Bell |
| R1-2111247 | Some issues on SPS for one DCI scheduling multiple PDSCHs case | CATT |
| R1-2111470 | NR channelization for the 57 – 71 GHz band | Ericsson |
| R1-2111928 | Additional SLS results on channel access | Huawei, HiSilicon |
| 8.3 | Enhanced Industrial Internet of Things (IoT) and URLLC | |
| R1-2112429 | Introduction of UE initiating a channel occupancy in semi-static channel access mode for enhanced IIoT and URLLC operation on shared spectrum for NR | Ericsson |
| R1-2112444 | Introduction of IIoT/URLLC enhancements in NR | Samsung |
| R1-2112475 | Introduction of Rel-17 enhanced IIoT and URLLC | Huawei |
| R1-2112484 | Introduction of enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication (URLLC) support for NR | Nokia |
| R1-2112514 | Introduction of IIoT/URLLC enhancements in NR | Qualcomm |
| R1-2112760 | Summary of [107-e-R17-RRC-IIoT-URLLC] Email discussion on Rel-17 RRC parameters for IIoT and URLLC | Moderator (Nokia) |
| R1-2112761 | List of agreements of Rel-17 URLLC/IIoT WI (post RAN1#107-e) | WI rapporteur (Nokia) |
| R1-2112918 | Introduction of UE initiating a channel occupancy in semi-static channel access mode for enhanced IIoT and URLLC operation on shared spectrum for NR | Ericsson |
| R1-2112932 | Introduction of IIoT/URLLC enhancements in NR | Samsung |
| R1-2112944 | Introduction of Rel-17 enhanced IIoT and URLLC | Huawei |
| R1-2112950 | Introduction of enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication (URLLC) support for NR | Nokia |
| R1-2112959 | Introduction of IIoT/URLLC enhancements in NR | Qualcomm |
| R1-2112984 | Introduction of enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication (URLLC) support for NR | Intel Corporation |
| 8.3.1 | UE feedback enhancements for HARQ-ACK | |
| R1-2110818 | UE feedback enhancements for HARQ-ACK | Huawei, HiSilicon |
| R1-2110914 | Discussion on HARQ-ACK enhancements for eURLLC | ZTE |
| R1-2111005 | Remaining issues on HARQ-ACK enhancements for Rel-17 URLLC | vivo |
| R1-2111094 | Discussion on HARQ-ACK feedback enhancements for Rel-17 URLLC | Spreadtrum Communications |
| R1-2111139 | HARQ-ACK Feedback Enhancements for URLLC/IIoT | Nokia, Nokia Shanghai Bell |
| R1-2111142 | Moderator summary #1 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2111188 | HARQ-ACK Enhancements for IIoT/URLLC | Ericsson |
| R1-2111248 | UE feedback enhancements for HARQ-ACK | CATT |
| R1-2111341 | HARQ-ACK enhancements for Rel-17 URLLC/IIoT | OPPO |
| R1-2111390 | Remaining issues in HARQ-ACK enhancements for URLLC | Sony |
| R1-2111434 | Discussion on PUCCH carrier switching for HARQ feedback enhancement | China Telecom |
| R1-2111489 | Remaining open issues of UE HARQ feedback enhancements | Intel Corporation |
| R1-2111567 | UE feedback enhancements for HARQ-ACK | Xiaomi |
| R1-2111604 | Discussion on UE feeback enhancements for HARQ-ACK | CMCC |
| R1-2111678 | Discussion on UE feedback enhancements for HARQ-ACK | Panasonic |
| R1-2111704 | UE feedback enhancements for HARQ-ACK | NEC |
| R1-2111730 | On HARQ-ACK reporting enhancements | Samsung |
| R1-2111839 | HARQ enhancements for IIoT and URLLC | InterDigital, Inc. |
| R1-2111867 | HARQ-ACK feedback enhancements for URLLC | Apple |
| R1-2111942 | HARQ-ACK feedback enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2111988 | UE feedback enhancements for HARQ-ACK | ETRI |
| R1-2112052 | Discussion on UE feedback enhancement for HARQ-ACK | LG Electronics |
| R1-2112076 | Discussion on UE feedback enhancements for HARQ-ACK | FGI, Asia Pacific Telecom |
| R1-2112081 | UE feedback enhancements for HARQ-ACK | TCL Communication Ltd. |
| R1-2112102 | Discussion on HARQ-ACK feedback enhancements for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2112173 | On the UE feedback enhancements for HARQ-ACK | ITRI |
| R1-2112209 | HARQ-ACK enhancement for IOT and URLLC | Qualcomm Incorporated |
| R1-2112285 | On UE feedback enhancements for HARQ-ACK | MediaTek Inc. |
| R1-2112395 | UE feedback enhancements for HARQ-ACK for NR Rel-17 URLLC/IIoT | CAICT |
| R1-2112616 | Moderator summary #2 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2112757 | Moderator summary #3 on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| R1-2112758 | Final moderator summary on HARQ-ACK feedback enhancements for NR Rel-17 URLLC/IIoT | Moderator (Nokia) |
| 8.3.2 | Enhancements for unlicensed band URLLC/IIoT | |
| R1-2110820 | Uplink enhancements for URLLC in unlicensed controlled environments | Huawei, HiSilicon |
| R1-2110878 | UE initiated COT for semi-static channel access | FUTUREWEI |
| R1-2110915 | Discussion on unlicensed band URLLC/IIoT | ZTE |
| R1-2111006 | Remaining issues on enhancements for unlicensed band URLLC/IIoT | vivo |
| R1-2111095 | Discussion on enhancements for unlicensed band URLLC/IIoT | Spreadtrum Communications |
| R1-2111176 | Enhancements for unlicensed band URLLC/IIoT | NEC |
| R1-2111189 | Enhancements for IIoT/URLLC on Unlicensed Band | Ericsson |
| R1-2111249 | Discussion on remaining issues on enhancements for unlicensed band URLLC/IIoT | CATT |
| R1-2111342 | Enhancements for unlicensed band URLLC/IIoT | OPPO |
| R1-2111363 | UL enhancements for IIoT/URLLC in unlicensed controlled environment | Nokia, Nokia Shanghai Bell |
| R1-2111391 | Remaining issues in Unlicensed URLLC | Sony |
| R1-2111490 | Remaining Details for Enabling URLLC/IIoT in Unlicensed Band | Intel Corporation |
| R1-2111568 | Enhancement for unlicensed band URLLC IIoT | Xiaomi |
| R1-2111731 | Enhancements for unlicensed band URLLC/IIoT | Samsung |
| R1-2111840 | Enhancements for unlicensed band URLLC/IIoT | InterDigital, Inc. |
| R1-2111868 | URLLC uplink enhancements for unlicensed spectrum | Apple |
| R1-2111943 | Enhancements for unlicensed band URLLC/IIoT | Lenovo, Motorola Mobility |
| R1-2111989 | Remaining issues on enhancements for unlicensed band URLLC/IIoT | ETRI |
| R1-2112013 | Enhancements for unlicensed band URLLC/IIoT | Sharp |
| R1-2112053 | Discussion on unlicensed band URLLC/IIOT | LG Electronics |
| R1-2112210 | Uplink enhancements for URLLC in unlicensed controlled environments | Qualcomm Incorporated |
| R1-2112286 | On the enhancements for unlicensed band URLLC/IIoT | MediaTek Inc. |
| R1-2112386 | Remaining issues on enhancement for unlicensed URLLC/IIoT | WILUS Inc. |
| R1-2112545 | Summary#1 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2112546 | Summary#2 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2112547 | Summary#3 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2112548 | Summary#4 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2112549 | Summary#5 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| R1-2112550 | Summary#6 - Enhancements for IIOT/URLLC on Unlicensed Band | Moderator (Ericsson) |
| 8.3.3 | Intra-UE Multiplexing/Prioritization | |
| R1-2110819 | Intra-UE multiplexing enhancements | Huawei, HiSilicon |
| R1-2110916 | Discussion on enhanced intra-UE multiplexing | ZTE |
| R1-2111007 | Remaining issues on intra-UE Multiplexing/Prioritization for Rel-17 URLLC | vivo |
| R1-2111096 | Discussion on intra-UE multiplexing/prioritization | Spreadtrum Communications |
| R1-2111140 | On UL intra-UE prioritization and multiplexing enhancements | Nokia, Nokia Shanghai Bell |
| R1-2111190 | Intra-UE Multiplexing/Prioritization Enhancements for IIoT/URLLC | Ericsson |
| R1-2111250 | Intra-UE multiplexing and prioritization | CATT |
| R1-2111343 | Enhancements on intra-UE multiplexing/prioritization | OPPO |
| R1-2111359 | Discussion on Intra-UE Multiplexing/Prioritization | Quectel, Langbo |
| R1-2111392 | Remaining issues in Intra-UE UL Multiplexing | Sony |
| R1-2111436 | Discussion on Intra-UE multiplexing of different priority | Panasonic Corporation |
| R1-2111491 | Remaining open details of intra-UE uplink channel multiplexing and prioritization | Intel Corporation |
| R1-2111569 | Intra-UE multiplexing prioritization for URLLC IIoT | Xiaomi |
| R1-2111705 | Discussion on Intra-UE prioritization and multiplexing | NEC |
| R1-2111732 | Uplink intra-UE multiplexing and prioritization | Samsung |
| R1-2111791 | Intra-UE multiplexing and prioritization | InterDigital, Inc. |
| R1-2111869 | Intra-UE Multiplexing/Prioritization in Rel-17 | Apple |
| R1-2111944 | Intra-UE multiplexing enhancement for IIoT/URLLC | Lenovo, Motorola Mobility |
| R1-2111990 | Intra-UE Multiplexing/Prioritization | ETRI |
| R1-2112014 | Enhancements on intra-UE UCI multiplexing and channel collision resolution framework | Sharp |
| R1-2112054 | Discussion on Intra-UE multiplexing/prioritization | LG Electronics |
| R1-2112083 | Intra-UE multiplexing and prioritization | TCL Communication Ltd. |
| R1-2112103 | Discussion on intra-UE multiplexing/prioritization for Rel.17 URLLC | NTT DOCOMO, INC. |
| R1-2112174 | Discussion on intra-UE multiplexing | ITRI |
| R1-2112211 | Intra-UE multiplexing and prioritization for IOT and URLLC | Qualcomm Incorporated |
| R1-2112287 | Methods for intra-UE multiplexing and prioritization | MediaTek Inc. |
| R1-2112387 | Discussion on intra-UE multiplexing/prioritization for URLLC/IIoT | WILUS Inc. |
| R1-2112564 | Summary #1 of email thread [107-e-NR-R17-IIoT-URLLC-03] | Moderator (CATT) |
| R1-2112604 | Summary#1 of email thread [107-e-NR-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| R1-2112667 | Summary#2 of email thread [107-e-NR-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| R1-2112712 | Summary #2 of email thread [107-e-NR-R17-IIoT-URLLC-03] | Moderator (CATT) |
| R1-2112785 | Summary#3 of email thread [107-e-NR-R17-IIoT-URLLC-04] | Moderator (OPPO) |
| 8.3.4 | Other | |
| R1-2110917 | Discussion on propagation delay compensation enhancements | ZTE |
| R1-2111008 | Remaining issues on propagation delay compensation enhancements | vivo |
| R1-2111141 | Discussion on enhancements for PDC and CSI | Nokia, Nokia Shanghai Bell |
| R1-2111191 | Propagation Delay Compensation Enhancements for Time Synchronization | Ericsson |
| R1-2111251 | Discussion on propagation delay compensation enhancements | CATT |
| R1-2111344 | Enhancement for support of time synchronization | OPPO |
| R1-2111492 | Remaining open issues for propagation delay compensation | Intel Corporation |
| R1-2111733 | Discussion for propagation delay compensation enhancements | Samsung |
| R1-2111926 | Enhancements for support of time synchronization | Huawei, HiSilicon |
| R1-2112055 | Discussion on propagation delay compensation enhancements | LG Electronics |
| R1-2112212 | Enhancements for support of time synchronization for enhanced IIoT and URLLC | Qualcomm Incorporated |
| R1-2112476 | Feature lead summary#1 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2112477 | Feature lead summary#2 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2112694 | Summary #1 of [107-e-NR-R17-IIoT-URLLC-06] on remaining issues on CSI feedback enhancement | Moderator (InterDigital, Inc.) |
| R1-2112728 | Feature lead summary#3 on propagation delay compensation enhancements | Moderator (Huawei) |
| R1-2112729 | Draft LS on propagation delay compensation | Huawei |
| R1-2112834 | LS on propagation delay compensation | RAN1, Huawei |
| R1-2112835 | Final feature lead summary on propagation delay compensation enhancements | Moderator (Huawei) |
| 8.4 | Solutions for NR to support non-terrestrial networks (NTN) | |
| R1-2112432 | Introduction of NTN | Ericsson |
| R1-2112447 | Introduction of non-terrestrial network operation in NR | Samsung |
| R1-2112473 | Introduction of NR non-terrestrial networks (NTN) | Huawei |
| R1-2112486 | Introduction of solutions for NR to support non-terrestrial networks (NTN) | Nokia |
| R1-2112791 | Session notes for 8.4 (Solutions for NR to support non-terrestrial networks (NTN)) | Ad-Hoc Chair (Huawei) |
| R1-2112849 | Summary of [107-e-R17-RRC-NR-NTN] Email discussion on Rel-17 RRC parameters for NR to support NTN | Moderator (Thales) |
| R1-2112890 | 3GPP TSG-RAN WG1 Agreements under 8.4 up to eMeeting RAN1#107-e | WI rapporteur (Thales) |
| R1-2112921 | Introduction of NTN | Ericsson |
| R1-2112934 | Introduction of non-terrestrial network operation in NR | Samsung |
| R1-2112942 | Introduction of NR non-terrestrial networks (NTN) | Huawei |
| R1-2112952 | Introduction of solutions for NR to support non-terrestrial networks (NTN) | Nokia |
| 8.4.1 | Timing relationship enhancements | |
| R1-2110804 | Discussion on timing relationship enhancements for NTN | Huawei, HiSilicon |
| R1-2110899 | Remaining timing relation aspects for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2111009 | Remaining issues on timing relationship enhancements for NR-NTN | vivo |
| R1-2111097 | Discussion on timing relationship enhancements for NTN | Spreadtrum Communications |
| R1-2111177 | Discussion on timing relationship enhancements for NTN | NEC |
| R1-2111252 | Further discussion on timing relationship enhancements for NTN | CATT |
| R1-2111314 | Discussion on timing relationship enhancement | OPPO |
| R1-2111353 | Remaining issues for timing relationship enhancements in NTN | Zhejiang Lab |
| R1-2111370 | Timing relationship enhancements for NR-NTN | MediaTek Inc. |
| R1-2111393 | Calculation and application of timing relationship offsets | Sony |
| R1-2111413 | On timing relationship enhancements for NTN | Ericsson |
| R1-2111441 | Discussion on timing relationship enhancement for NTN | Baicells |
| R1-2111445 | Discussions on timing relationship enhancements in NTN | SK Telecom, ETRI |
| R1-2111493 | Remaining issues on timing relationships for NTN | Intel Corporation |
| R1-2111570 | Discussion on the remaining issues on the timing relationship enhancement for NTN | Xiaomi |
| R1-2111605 | Discussion on timing relationship enhancements for NTN | CMCC |
| R1-2111646 | Timing relationship for NTN | Panasonic Corporation |
| R1-2111652 | Timing relationship enhancements to support NTN | CAICT |
| R1-2111658 | Discussion on timing relationship for NR-NTN | ZTE |
| R1-2111734 | Timing relationship enhancements for NTN | Samsung |
| R1-2111820 | Remaining issues on timing relationship enhancement for NTN | InterDigital, Inc. |
| R1-2111870 | Timing Relationship Enhancements for NR NTN | Apple |
| R1-2111968 | Discussions on timing relationship enhancements in NTN | LG Electronics |
| R1-2112004 | Discussion on NTN timing relationship | Lenovo, Motorola Mobility |
| R1-2112104 | Discussion on timing relationship enhancements for NTN | NTT DOCOMO, INC. |
| R1-2112169 | Timing relationship enhancements for NTN | ITL |
| R1-2112213 | Enhancements on Timing Relationship for NTN | Qualcomm Incorporated |
| R1-2112507 | Feature lead summary#1 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2112533 | Feature lead summary#2 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2112612 | Feature lead summary#3 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2112647 | Feature lead summary#4 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2112652 | DRAFT reply LS on UE TA reporting | Ericsson |
| R1-2112716 | Feature lead summary#5 on timing relationship enhancements | Moderator (Ericsson) |
| R1-2112766 | Reply LS on UE TA reporting | RAN1, Ericsson |
| 8.4.2 | Enhancements on UL time and frequency synchronization | |
| R1-2110805 | Discussion on UL time and frequency synchronization enhancement for NTN | Huawei, HiSilicon |
| R1-2110900 | Remaining time and frequency synchronization aspects for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2111010 | Remaining issues on UL time and frequency synchronization enhancements for NR-NTN | vivo |
| R1-2111098 | Discussion on enhancements on UL time and frequency synchronization for NTN | Spreadtrum Communications |
| R1-2111122 | Considerations on UL timing and frequency synchronization in NTN | THALES |
| R1-2111123 | FL Summary #1 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2111124 | FL Summary #2 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2111125 | FL Summary #3 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2111126 | FL Summary #4 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2111127 | FL Summary #5 on enhancements on UL time and frequency synchronization for NR NTN | Moderator (Thales) |
| R1-2111178 | Discussion on UL time synchronization for NR NTN | NEC |
| R1-2111253 | Further discussion on UL time and frequency synchronization enhancement for NTN | CATT |
| R1-2111315 | Discussion on UL time and frequency synchronization | OPPO |
| R1-2111355 | Enhancements on UL time and frequency synchronization | PANASONIC R&D Center Germany |
| R1-2111371 | Enhancements on UL Time and Frequency Synchronisation for NR-NTN | MediaTek Inc. |
| R1-2111394 | Considerations on UL time synchronisation | Sony |
| R1-2111412 | Frequency Synchronization Considerations | Lockheed Martin |
| R1-2111414 | On UL time and frequency synchronization enhancements for NTN | Ericsson |
| R1-2111442 | Discussion on UL time and frequency synchronization enhancement for NTN | Baicells |
| R1-2111494 | Remaining issues on synchronization for NTN | Intel Corporation |
| R1-2111571 | Discussion on UL time and frequency synchronization for NTN | Xiaomi |
| R1-2111606 | Enhancements on UL time and frequency synchronization for NTN | CMCC |
| R1-2111659 | Discussion on UL synchronization for NR-NTN | ZTE |
| R1-2111735 | Enhancements on UL time and frequency synchronization for NTN | Samsung |
| R1-2111790 | Discussion on UL Time Synchronization for NTN | Fraunhofer IIS - Fraunhofer HHI |
| R1-2111821 | Remaining issues on UL time/frequency synchronization for NTN | InterDigital, Inc. |
| R1-2111871 | Uplink Time and Frequency Synchronization for NR NTN | Apple |
| R1-2111969 | Discussions on UL time and frequency synchronization enhancements in NTN | LG Electronics |
| R1-2112005 | Discussion on NTN uplink time synchronization | Lenovo, Motorola Mobility |
| R1-2112105 | Discussion on UL time and frequency synchronization enhancements for NTN | NTT DOCOMO, INC. |
| R1-2112214 | UL time and frequency synchronization for NTN | Qualcomm Incorporated |
| 8.4.3 | Enhancements on HARQ | |
| R1-2110806 | Discussion on HARQ enhancement for NTN | Huawei, HiSilicon |
| R1-2110901 | Remaining aspects related to HARQ for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2111011 | Remaining issues on HARQ enhancements for NR-NTN | vivo |
| R1-2111099 | Discussion on enhancements on HARQ for NTN | Spreadtrum Communications |
| R1-2111179 | Discussion on HARQ enhancements for NR NTN | NEC |
| R1-2111254 | HARQ operation enhancement for NTN | CATT |
| R1-2111316 | Discussion on HARQ enhancements | OPPO |
| R1-2111372 | Enhancements on HARQ for NR NTN | MediaTek Inc. |
| R1-2111395 | Enhancements on HARQ for NTN | Sony |
| R1-2111415 | On HARQ enhancements for NTN | Ericsson |
| R1-2111443 | Discussion on HARQ enhancement for NTN | Baicells |
| R1-2111572 | Discussion on the HARQ enhancement for NTN | Xiaomi |
| R1-2111607 | Enhancements on HARQ for NTN | CMCC |
| R1-2111647 | HARQ enhancement for NTN | Panasonic Corporation |
| R1-2111653 | Enhancements on HARQ to support NTN | CAICT |
| R1-2111660 | Discussion on HARQ for NR-NTN | ZTE |
| R1-2111736 | Enhancements on HARQ for NTN | Samsung |
| R1-2111822 | Remaining issues on HARQ enhancement for NTN | InterDigital, Inc. |
| R1-2111872 | HARQ Enhancements for NR NTN | Apple |
| R1-2111970 | Discussions on HARQ enhancements in NTN | LG Electronics |
| R1-2111991 | Discussion on HARQ Enhancements for NTN | ETRI |
| R1-2112106 | Discussion on HARQ enhancements for NR NTN | NTT DOCOMO, INC. |
| R1-2112215 | Enhancements on HARQ for NTN | Qualcomm Incorporated |
| R1-2112335 | Discussion on HARQ enhancements for NTN | ITL |
| R1-2112555 | Summary#1 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE Corporation) |
| R1-2112663 | Summary#2 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE Corporation) |
| R1-2112664 | Summary#3 of AI 8.4.3 for HARQ in NTN | Moderator (ZTE Corporation) |
| 8.4.4 | Other | |
| R1-2110902 | Remaining other aspects for NR over NTN | Nokia, Nokia Shanghai Bell |
| R1-2110903 | Discussion on other aspects for NR-NTN | BUPT |
| R1-2111012 | Remaining issues on other aspects for NR-NTN | vivo |
| R1-2111100 | Discussion on beam management and other aspects for NTN | Spreadtrum Communications |
| R1-2111180 | Remaining issues for NR NTN | NEC |
| R1-2111255 | Other aspects for NTN | CATT |
| R1-2111317 | Discussion on beam management | OPPO |
| R1-2111396 | Discussion on beam management and polarization for NTN | Sony |
| R1-2111416 | On other enhancements for NTN | Ericsson |
| R1-2111444 | Discussion on beam management and other consideration for NTN | Baicells |
| R1-2111573 | Discussion on other design aspects for NTN | Xiaomi |
| R1-2111608 | Other Aspects for NTN | CMCC |
| R1-2111661 | Discussion on additional enhancement for NR-NTN | ZTE |
| R1-2111706 | Beam management and polarization signaling for NTN | Panasonic |
| R1-2111737 | Remaining issues for NTN | Samsung |
| R1-2111823 | Remaining issues on beam management for NTN | InterDigital, Inc. |
| R1-2111873 | Other Aspects of NR NTN | Apple |
| R1-2111924 | Discussion on other design aspects for NTN | Huawei, HiSilicon |
| R1-2111971 | Discussions on other aspects of NTN | LG Electronics |
| R1-2112107 | Discussion on other aspects for NR NTN | NTT DOCOMO, INC. |
| R1-2112216 | BWP operation and other issues for NTN | Qualcomm Incorporated |
| R1-2112270 | Issues on NTN with Transparent Payload | III |
| R1-2112532 | Summary#1 of the discussions on other enhancements | Moderator (OPPO) |
| 8.5 | NR Positioning Enhancements | |
| R1-2112426 | Introduction of NR positioning enhancements | Intel Corporation |
| R1-2112487 | Introduction of NR Positioning Enhancements | Nokia |
| R1-2112508 | FL Summary for Rel-17 RRC parameters for positioning enhancement | Moderator (CATT) |
| R1-2112509 | FL Summary #2 for Rel-17 RRC parameters for positioning enhancement | Moderator (CATT) |
| R1-2112792 | Session notes for 8.5 (NR Positioning Enhancements) | Ad-Hoc Chair (Huawei) |
| R1-2112915 | Introduction of NR positioning enhancements | Intel Corporation |
| R1-2112953 | Introduction of NR Positioning Enhancements | Nokia |
| 8.5.1 | Accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | |
| R1-2110850 | Remaining issues of mitigating Rx/Tx timing error | Huawei, HiSilicon |
| R1-2110956 | Positioning accuracy improvement by mitigating timing delay | ZTE |
| R1-2111013 | Remaining issues on potential enhancements for RX/TX timing delay mitigating | vivo |
| R1-2111256 | Remaining issues on mitigating UE and gNB Rx/Tx timing errors | CATT |
| R1-2111289 | Enhancement of timing-based positioning by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | OPPO |
| R1-2111364 | Views on mitigating UE and gNB Rx/Tx timing errors | Nokia, Nokia Shanghai Bell |
| R1-2111397 | Remaining issues on mitigating Rx/Tx timing delays | Sony |
| R1-2111495 | Remaining Details of UE/gNB RX/TX Timing Errors Mitigation | Intel Corporation |
| R1-2111609 | Discussion on mitigation of gNB/UE Rx/Tx timing errors | CMCC |
| R1-2111738 | Discussion on accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Samsung |
| R1-2111797 | Discussion on accuracy improvements by mitigating timing delays | InterDigital, Inc. |
| R1-2111874 | Positioning accuracy enhancements under timing errors | Apple |
| R1-2111973 | Discussion on accuracy improvement by mitigating UE Rx/Tx and gNB Rx/Tx timing delays | LG Electronics |
| R1-2112071 | Mitigation of RX/TX timing delays for higher accuracy | MediaTek Inc. |
| R1-2112108 | Discussion on mitigating UE and gNB Rx/Tx timing delays | NTT DOCOMO, INC. |
| R1-2112217 | Remaining Issues on Timing Error Mitigations for improved Accuracy | Qualcomm Incorporated |
| R1-2112323 | Considerations for mitigation of Tx/Rx Delays | Lenovo, Motorola Mobility |
| R1-2112339 | Techniques mitigating Rx/Tx timing delays | Ericsson |
| R1-2112510 | FL Summary for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2112511 | FL Summary #2 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2112512 | FL Summary #3 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2112513 | FL Summary #4 for accuracy improvements by mitigating UE Rx/Tx and/or gNB Rx/Tx timing delays | Moderator (CATT) |
| R1-2112967 | Draft LS on the reporting of the Tx TEG association information | Moderator (CATT) |
| R1-2112968 | LS on the reporting of the Tx TEG association information | RAN1, CATT |
| 8.5.2 | Accuracy improvements for UL-AoA positioning solutions | |
| R1-2110851 | Remaining issues of UL AoA enhancements | Huawei, HiSilicon |
| R1-2110957 | Remaining issues on UL-AOA positioning solutions | ZTE |
| R1-2111014 | Remaining issues on potential enhancements for UL-AoA method | vivo |
| R1-2111257 | Remaining issues on enhancements for UL-AoA positioning method | CATT |
| R1-2111290 | Enhancements for UL AoA Positioning | OPPO |
| R1-2111365 | Views on enhancing UL AoA | Nokia, Nokia Shanghai Bell |
| R1-2111398 | Remaining aspects of UL-AoA enhancements | Sony |
| R1-2111496 | Remaining Details of NR Positioning UL-AoA Enhancements | Intel Corporation |
| R1-2111739 | Discussion on accuracy improvements for UL-AoA positioning solutions | Samsung |
| R1-2111798 | Enhancements for UL-AoA positioning solutions | InterDigital, Inc. |
| R1-2111875 | Positioning Accuracy enhancements for UL-AoA | Apple |
| R1-2111974 | Discussion on accuracy improvement for UL-AoA positioning | LG Electronics |
| R1-2112109 | Discussion on UL-AoA positioning enhancements | NTT DOCOMO, INC. |
| R1-2112218 | Remaining Issues on Potential Enhancements on UL-AOA positioning | Qualcomm Incorporated |
| R1-2112340 | Enhancements of UL-AoA positioning solutions | Ericsson |
| R1-2112566 | Feature Lead Summary#1 for E-mail Discussion [107-e-NR-ePos-02] | Moderator (Intel Corporation) |
| R1-2112567 | Feature Lead Summary#2 for E-mail Discussion [107-e-NR-ePos-02] | Moderator (Intel Corporation) |
| R1-2112568 | Feature Lead Summary#3 for E-mail Discussion [107-e-NR-ePos-02] | Moderator (Intel Corporation) |
| R1-2112739 | Draft LS on ARP association with UL measurements for NR positioning | Moderator (Intel Corporation) |
| R1-2112740 | LS on ARP association with UL measurements for NR positioning | RAN1, Intel Corporation |
| R1-2112743 | Draft LS on UL SRS-RSRPP definition | Moderator (Intel Corporation) |
| R1-2112744 | LS on UL SRS-RSRPP definition | RAN1, Intel Corporation |
| 8.5.3 | Accuracy improvements for DL-AoD positioning solutions | |
| R1-2110852 | Remaining issues of DL AoD enhancements | Huawei, HiSilicon |
| R1-2110958 | Accuracy improvement for DL-AoD positioning solutions | ZTE |
| R1-2111015 | Remaining issues on potential enhancements for DL-AoD method | vivo |
| R1-2111258 | Remaining issues on enhancements for DL-AoD positioning method | CATT |
| R1-2111291 | Enhancements for DL-AoD positioning | OPPO |
| R1-2111366 | Views on enhancing DL AoD | Nokia, Nokia Shanghai Bell |
| R1-2111399 | Remaining aspects of DL-AoD enhancements | Sony |
| R1-2111497 | Remaining Details of DL-AoD Enhancements for NR Positioning | Intel Corporation |
| R1-2111574 | Accuracy improvements for DL-AoD positioning solutions | Xiaomi |
| R1-2111610 | Discussion on DL-AoD enhancements | CMCC |
| R1-2111654 | Discussion on enhancements for DL-AoD positioning | CAICT |
| R1-2111740 | Discussion on accuracy improvements for DL-AoD positioning solutions | Samsung |
| R1-2111799 | Enhancements for DL-AoD positioning solutions | InterDigital, Inc. |
| R1-2111876 | Positioning Accuracy enhancements for DL-AoD | Apple |
| R1-2111975 | Discussion on accuracy improvement for DL-AoD positioning | LG Electronics |
| R1-2112072 | Accuracy enhancement for DL-AOD technique | MediaTek Inc. |
| R1-2112110 | Discussion on DL-AoD positioning enhancements | NTT DOCOMO, INC. |
| R1-2112219 | Remaining Issues on Potential Enhancements for DL-AoD positioning | Qualcomm Incorporated |
| R1-2112324 | Remaining issues on DL-AoD Positioning Enhancements | Lenovo, Motorola Mobility |
| R1-2112341 | Enhancements of DL-AoD positioning solutions | Ericsson |
| R1-2112367 | DL-AoD positioning enhancements | Fraunhofer IIS, Fraunhofer HHI |
| R1-2112641 | FL summary #1 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2112642 | FL summary #2 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2112643 | FL summary #3 for AI 8.5.3 Accuracy improvements for DL-AoD positioning solutions | Moderator (Ericsson) |
| R1-2112843 | [DRAFT] LS on TRP beam/antenna information | Moderator (Ericsson) |
| R1-2112844 | LS on TRP beam/antenna information | RAN1, Ericsson |
| 8.5.4 | Latency improvements for both DL and DL+UL positioning methods | |
| R1-2110853 | Enhancements to positioning latency improvements | Huawei, HiSilicon |
| R1-2110959 | Discussion on latency reduction for NR positioning | ZTE |
| R1-2111016 | Remaining issues on latency enhancement for NR positioning | vivo |
| R1-2111259 | Remaining issues on latency reduction for NR positioning | CATT |
| R1-2111292 | Enhancements on Latency Reduction in NR Positioning | OPPO |
| R1-2111367 | Views on PHY Latency Reductions | Nokia, Nokia Shanghai Bell |
| R1-2111400 | Remaining issues on latency improvements for NR positioning | Sony |
| R1-2111435 | Discussion on latency improvement for positioning | China Telecom |
| R1-2111498 | Remaining Open Aspects of NR Positioning Latency Reduction | Intel Corporation |
| R1-2111575 | Latency improvements for both DL and DL+UL positioning method | Xiaomi |
| R1-2111611 | Discussion on latency improvement for positioning | CMCC |
| R1-2111741 | Discussion on latency improvements for both DL and DL+UL positioning methods | Samsung |
| R1-2111800 | Latency improvements for both DL and DL+UL positioning methods | InterDigital, Inc. |
| R1-2111877 | Views on Rel-17 positioning latency reduction | Apple |
| R1-2111976 | Discussion on latency improvements for NR positioning | LG Electronics |
| R1-2112073 | Physical latency improvement aspects | MediaTek Inc. |
| R1-2112111 | Discussion on latency improvements for both DL and DL+UL positioning methods | NTT DOCOMO, INC. |
| R1-2112220 | Remaining issues on Latency Improvements for Positioning | Qualcomm Incorporated |
| R1-2112325 | Remaining issues on Positioning Latency Reduction | Lenovo, Motorola Mobility |
| R1-2112342 | Latency improvements for both DL and DL+UL positioning methods | Ericsson |
| R1-2112411 | Draft LS on lower Rx beam sweeping factor for latency improvement | Moderator (Huawei) |
| R1-2112457 | Summary #1 of [107-e-NR-ePos-04] latency improvements | Moderator (Huawei) |
| R1-2112458 | Summary #2 of [107-e-NR-ePos-04] latency improvements | Moderator (Huawei) |
| R1-2112459 | Summary #3 of [107-e-NR-ePos-04] latency improvements | Moderator (Huawei) |
| R1-2112767 | LS on lower Rx beam sweeping factor for latency improvement | RAN1, Huawei |
| R1-2112783 | [DRAFT] Draft LS on latency improvement for PRS measurement with MG | Moderator (Huawei) |
| R1-2112784 | LS on latency improvement for PRS measurement with MG | RAN1, Huawei |
| R1-2112880 | Draft LS on PRS processing window | Moderator (Huawei) |
| R1-2112881 | LS on PRS processing window | RAN1, Huawei |
| R1-2112882 | Draft LS on the condition of PRS measurement outside the MG | Moderator (Huawei) |
| R1-2112883 | LS on the condition of PRS measurement outside the MG | RAN1, Huawei |
| 8.5.5 | Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation | |
| R1-2110854 | Remaining issues of NLOS mitigation and multi-path reporting | Huawei, HiSilicon |
| R1-2110860 | Enhancements on NLoS mitigation for NR positioning | PML |
| R1-2110960 | Enhancements on NLOS and Multi-path mitigation for NR positioning | ZTE |
| R1-2111017 | Remaining issues on potential enhancements for multipath/NLOS mitigation | vivo |
| R1-2111260 | Remaining issues on information reporting from UE and gNB for multipath/NLOS mitigation | CATT |
| R1-2111293 | Discussion on multipath/NLOS mitigation for NR positioning | OPPO |
| R1-2111368 | Views on LoS/NLoS Identification and Mitigation | Nokia, Nokia Shanghai Bell |
| R1-2111401 | Remaining issues on multipath/NLOS mitigation for NR positioning | Sony |
| R1-2111499 | Remaining Details of NLOS Mitigation Solutions for NR Positioning | Intel Corporation |
| R1-2111576 | Potential enhancements for multipath/NLOS mitigation | Xiaomi |
| R1-2111742 | Discussion on potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation | Samsung |
| R1-2111801 | Discussion on multipath/NLOS mitigation for positioning | InterDigital, Inc. |
| R1-2111878 | Views on potential enhancements for NLOS mitigation in Rel-17 positioning | Apple |
| R1-2111977 | Discussion on multipath/NLOS mitigation for positioning | LG Electronics |
| R1-2112112 | Discussion on multipath/NLOS mitigation for NR positioning | NTT DOCOMO, INC. |
| R1-2112221 | Remaining Issues on Multipath Reporting in NR Positioning | Qualcomm Incorporated |
| R1-2112326 | Remaining issues on NLOS/Multipath Reporting | Lenovo, Motorola Mobility |
| R1-2112343 | Potential enhancements of information reporting from UE and gNB for multipath/NLOS mitigation | Ericsson |
| R1-2112368 | Potential positioning enhancements for multipath/NLOS mitigation | Fraunhofer IIS, Fraunhofer HHI |
| R1-2112492 | Feature Lead Summary #1 for Potential multipath/NLOS mitigation | Moderator (Nokia) |
| R1-2112493 | Feature Lead Summary #2 for Potential multipath/NLOS mitigation | Moderator (Nokia) |
| R1-2112494 | Feature Lead Summary #3 for Potential multipath/NLOS mitigation | Moderator (Nokia) |
| R1-2112495 | Feature Lead Summary #4 for Potential multipath/NLOS mitigation | Moderator (Nokia) |
| 8.5.6 | Other | |
| R1-2110961 | Discussion on items led by RAN2 for NR positioning | ZTE |
| R1-2111018 | Remaining issues on inactive state positioning and on-demand PRS | vivo |
| R1-2111261 | Remaining issues on on-demand DL PRS and positioning for UEs in RRC_ INACTIVE state | CATT |
| R1-2111294 | Discussion on positioning for UE in RRC_INACTIVE and on-demand PRS | OPPO |
| R1-2111369 | Additional views on Inactive Mode Positioning and on-demand PRS | Nokia, Nokia Shanghai Bell |
| R1-2111402 | Remaining Aspects of On-demand PRS and positioning in RRC Inactive Mode | Sony |
| R1-2111500 | Remaining Details for On-demand DL PRS Signaling and NR Positioning in RRC_INACTIVE state | Intel Corporation |
| R1-2111577 | On-demand PRS and positioning for UE in RRC_INACTIVE state | Xiaomi |
| R1-2111596 | Positioning in RRC_INACTIVE mode and on-demand PRS request | Quectel |
| R1-2111612 | Discussion on RAN2-led items for positioning | CMCC |
| R1-2111655 | Discussion on enhancements of INACTIVE mode positioning and on-demand PRS | CAICT |
| R1-2111743 | Discussion on on demand positioning and positioning in inactive state | Samsung |
| R1-2111802 | On-demand PRS and positioning during INACTIVE mode | InterDigital, Inc. |
| R1-2111879 | DL-PRS conflict resolution for UE in RRC_INACTIVE | Apple |
| R1-2111932 | Discussion on INACTIVE state positioning and on-demand PRS | Huawei, HiSilicon |
| R1-2111978 | Discussion on other enhancements for positioning | LG Electronics |
| R1-2112222 | Remaining issues on enhancements Related to On Demand PRS And Positioning in RRC Inactive State | Qualcomm Incorporated |
| R1-2112327 | Discussion on On-Demand PRS and RRC_INACTIVE Positioning | Lenovo, Motorola Mobility |
| R1-2112344 | Further details for on-demand PRS reception and SRS in RRC_INACTIVE | Ericsson |
| R1-2112369 | Considerations for on-demand PRS and positioning in RRC_INACTIVE state | Fraunhofer IIS, Fraunhofer HHI |
| R1-2112569 | Feature Lead Summary#1 for E-mail Discussion [107-e-NR-ePos-06] | Moderator (Intel Corporation) |
| R1-2112570 | Feature Lead Summary#2 for E-mail Discussion [107-e-NR-ePos-06] | Moderator (Intel Corporation) |
| R1-2112571 | Feature Lead Summary#3 for E-mail Discussion [107-e-NR-ePos-06] | Moderator (Intel Corporation) |
| R1-2112741 | Draft LS on DL PRS processing by UEs in RRC_INACTIVE state | Moderator (Intel Corporation) |
| R1-2112742 | LS on DL PRS processing by UEs in RRC_INACTIVE state | RAN1, Intel Corporation |
| R1-2112845 | Draft LS on configuration and transmission of SRS for positioning in RRC_INACTIVE state | Moderator (Intel Corporation) |
| R1-2112846 | LS on configuration and transmission of SRS for positioning in RRC_INACTIVE state | RAN1, Intel Corporation |
| 8.6 | Support of Reduced Capability NR Devices | |
| R1-2112448 | Introduction of UEs with reduced capabilities in NR | Samsung |
| R1-2112488 | Introduction of NR reduced capability NR devices | Nokia |
| R1-2112504 | FL summary on RAN1 RRC parameter list for Rel-17 NR RedCap | Moderator (Ericsson) |
| R1-2112505 | Draft RAN1 RRC parameter list for Rel-17 NR RedCap | Moderator (Ericsson) |
| R1-2112506 | RAN1 agreements for Rel-17 NR RedCap | Rapporteur (Ericsson) |
| R1-2112793 | Session notes for 8.6 (Support of Reduced Capability NR Devices) | Ad-hoc Chair (CMCC) |
| R1-2112935 | Introduction of UEs with reduced capabilities in NR | Samsung |
| R1-2112954 | Introduction of NR reduced capability NR devices | Nokia |
| 8.6.1.1 | Aspects related to reduced maximum UE bandwidth | |
| R1-2110769 | Reduced maximum UE bandwidth for RedCap | Ericsson |
| R1-2110801 | Reduced maximum UE bandwidth | Huawei, HiSilicon |
| R1-2110892 | Bandwidth Reduction for RedCap UEs | FUTUREWEI |
| R1-2111019 | Remaining issues on reduced maximum UE bandwidth | vivo, Guangdong Genius |
| R1-2111066 | Bandwidth reduction for reduced capability NR devices | ZTE, Sanechips |
| R1-2111101 | Discussion on aspects related to reduced maximum UE bandwidth | Spreadtrum Communications |
| R1-2111129 | Bandwidth Reduction for Reduced Capability Devices | Nokia, Nokia Shanghai Bell |
| R1-2111262 | Discussion on reduced maximum UE bandwidth | CATT |
| R1-2111322 | Discussion on reduced UE bandwidth | OPPO |
| R1-2111403 | Discussion on reduced maximum UE bandwidth for RedCap | Sony |
| R1-2111501 | On reduced max UE BW for RedCap | Intel Corporation |
| R1-2111578 | Discussion on the remaining issues of reduced UE bandwidth for RedCap | Xiaomi |
| R1-2111595 | Discussion on aspects related to reduced maximum UE bandwidth | ASUSTeK |
| R1-2111613 | Discussion on reduced maximum UE bandwidth | CMCC |
| R1-2111744 | UE complexity reduction | Samsung |
| R1-2111880 | Reduced maximum UE bandwidth for Redcap | Apple |
| R1-2111957 | Discussion on BWP operation for RedCap | NEC |
| R1-2111963 | Discussion on reduced maximum bandwidth for RedCap UEs | InterDigital, Inc. |
| R1-2112006 | Reduced maximum UE bandwidth for RedCap | Lenovo, Motorola Mobility |
| R1-2112015 | Discussion on reduced maximum UE bandwidth | Sharp |
| R1-2112056 | Aspects related to the reduced maximum UE bandwidth of RedCap | LG Electronics |
| R1-2112084 | Aspects related to reduced maximum UE bandwidth for RedCap | Panasonic Corporation |
| R1-2112113 | Discussion on reduced maximum UE bandwidth for RedCap | NTT DOCOMO, INC. |
| R1-2112223 | BW Reduction for RedCap UE | Qualcomm Incorporated |
| R1-2112283 | On reduced maximum bandwidth for RedCap UEs | MediaTek Inc. |
| R1-2112376 | On aspects related to reduced maximum UE BW | Nordic Semiconductor ASA |
| R1-2112497 | FL summary #1 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2112498 | FL summary #2 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2112499 | FL summary #3 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2112500 | FL summary #4 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2112501 | FL summary #5 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2112502 | FL summary #6 on reduced maximum UE bandwidth for RedCap | Moderator (Ericsson) |
| R1-2112801 | [Draft] LS on use of NCD-SSB in initial DL BWP used for paging for RedCap UE | Ericsson |
| R1-2112802 | LS on use of NCD-SSB or CSI-RS in DL BWPs for RedCap UE | RAN1, Ericsson |
| 8.6.1.2 | Other aspects | |
| R1-2110770 | Duplex operation for RedCap | Ericsson |
| R1-2111020 | Remaining issues on RedCap half-duplex operation | vivo, Guangdong Genius |
| R1-2111067 | HD-FDD for reduced capability NR devices | ZTE, Sanechips |
| R1-2111102 | Discussion on other aspects for RedCap | Spreadtrum Communications |
| R1-2111130 | Other UE Complexity Reduction Aspects | Nokia, Nokia Shanghai Bell |
| R1-2111263 | Discussion on other aspects related to complexity reduction | CATT |
| R1-2111323 | Other remaining issues for Reduced Capability NR Devices | OPPO |
| R1-2111432 | Remaining issues on other aspects for RedCap | China Telecom |
| R1-2111502 | On other aspects of complexity reduction for RedCap UEs | Intel Corporation |
| R1-2111579 | Discussion on the remaining issues of HD-FDD for RedCap | Xiaomi |
| R1-2111614 | Discussion on collision handling of HD-FDD operation | CMCC |
| R1-2111745 | Other aspects for complexity reduction for RedCap Ues | Samsung |
| R1-2111881 | Other UE complexity reduction aspects for RedCap | Apple |
| R1-2111922 | Other complexity reduction aspects for RedCap UEs | Huawei, HiSilicon |
| R1-2111964 | Duplex operation for RedCap UEs | InterDigital, Inc. |
| R1-2112016 | Discussion on duplex operation for redcap UEs | Sharp |
| R1-2112057 | Aspects related to the duplex operation of RedCap | LG Electronics |
| R1-2112086 | Other aspects for UE complexity reduction for RedCap | Panasonic Corporation |
| R1-2112114 | Discussion on other aspects for RedCap | NTT DOCOMO, INC. |
| R1-2112224 | Other Aspects of RedCap UE Complexity Reduction | Qualcomm Incorporated |
| R1-2112284 | On half duplex operation for RedCap UEs | MediaTek Inc. |
| R1-2112377 | On aspects related to duplex operation | Nordic Semiconductor ASA |
| R1-2112388 | Remining issue on duplex operation for RedCap UE | WILUS Inc. |
| R1-2112544 | FL summary #1 on other aspects for RedCap | Moderator (Qualcomm) |
| R1-2112600 | FL summary #2 on other aspects for RedCap | Moderator (Qualcomm) |
| R1-2112601 | FL summary #3 on other aspects for RedCap | Moderator (Qualcomm) |
| 8.6.2 | RAN1 aspects for RAN2-led features for RedCap | |
| R1-2110771 | RAN1 aspects for RAN2-led features for RedCap | Ericsson |
| R1-2110802 | RAN1 aspects of RedCap UE type and identification | Huawei, HiSilicon |
| R1-2111021 | Remaining issues on higher layer support for RedCap | vivo, Guangdong Genius |
| R1-2111068 | Higher layer support of Reduced Capability NR devices | ZTE, Sanechips |
| R1-2111131 | Higher layer support of Reduced Capability NR Devices | Nokia, Nokia Shanghai Bell |
| R1-2111202 | Discussion on RAN1 aspects for RAN2-led features for RedCap | TCL Communication Ltd. |
| R1-2111264 | Discussion on higher layer support of RedCap | CATT |
| R1-2111324 | Mechanism in higher&PHY layer for Reduced Capability NR Devices | OPPO |
| R1-2111433 | Remaining issues on RAN1 aspects for RAN2-led features for RedCap | China Telecom |
| R1-2111503 | On RAN1 aspects for RAN2-led features for RedCap | Intel Corporation |
| R1-2111580 | Discussion on the remaining issues of higher layer related topics for RedCap | Xiaomi |
| R1-2111615 | Discussion on higher layer support of RedCap UE | CMCC |
| R1-2111746 | RAN1 aspects for RAN2-led features for RedCap | Samsung |
| R1-2111882 | RAN1 aspects for RAN2-led features for RedCap | Apple |
| R1-2111883 | FL summary #1 on RAN1 aspects for RAN2-led features for RedCap | Moderator (Apple) |
| R1-2111958 | Discussion on RAN1 aspects for RAN2-led features for RedCap | NEC |
| R1-2111965 | RAN1 aspects of RAN2-led RedCap features | InterDigital, Inc. |
| R1-2112007 | RAN1 aspects for RAN2-led features for RedCap | Lenovo, Motorola Mobility |
| R1-2112017 | RAN1 aspects for RAN2-led features for RedCap | Sharp |
| R1-2112058 | RAN1 aspects for RAN2-led features for RedCap | LG Electronics |
| R1-2112115 | Discussion on RAN1 aspects for RAN2-led features for RedCap | NTT DOCOMO, INC. |
| R1-2112225 | Cross Layer Design Considerations for RedCap Device | Qualcomm Incorporated |
| R1-2112330 | RAN1 aspects for RAN2-led features for RedCap | Panasonic Corporation |
| R1-2112389 | Remaining issue on higher layer support of Redcap UE | WILUS Inc. |
| R1-2112654 | FL summary #2 on RAN1 aspects for RAN2-led features for RedCap | Moderator (Apple) |
| R1-2112818 | FL summary #3 on RAN1 aspects for RAN2-led features for RedCap | Moderator (Apple) |
| 8.6.3 | Other | |
| R1-2110772 | UE cost reduction estimates for RedCap | Ericsson |
| R1-2111022 | Remaining issues on L1 reduced capability signaling | vivo, Guangdong Genius |
| R1-2111069 | Consideration on PRACH resource configuration for RedCap and CovEnh | ZTE, Sanechips |
| R1-2111132 | On other aspects of RedCap | Nokia, Nokia Shanghai Bell |
| R1-2111265 | Views on remaining issues of RedCap | CATT |
| R1-2111581 | Discussion on the transmission of system information for RedCap | Xiaomi |
| R1-2111616 | Discussion on other aspects of RedCap UE | CMCC |
| R1-2111923 | On RedCap UE RF retuning | Huawei, HiSilicon |
| R1-2111966 | Considerations for initial BWP for RedCap UEs | InterDigital, Inc. |
| R1-2112059 | Discussion on other aspects of RedCap | LG Electronics |
| 8.7 | UE Power Saving Enhancements | |
| R1-2112449 | Introduction of UE power savings enhancements in NR | Samsung |
| R1-2112474 | Introduction of Rel-17 UE power saving enhancements | Huawei |
| R1-2112491 | Introduction of NR UE Power Saving Enhancements | Nokia |
| R1-2112794 | Session notes for 8.7 (UE Power Saving Enhancements) | Ad-hoc Chair (CMCC) |
| R1-2112876 | Session notes for 8.7 (UE Power Saving Enhancements) | Ad-hoc Chair (CMCC) |
| R1-2112887 | Summary of email discussion on Rel-17 RRC parameters for UE power saving | Moderator (MediaTek Inc.) |
| R1-2112936 | Introduction of UE power savings enhancements in NR | Samsung |
| R1-2112943 | Introduction of Rel-17 UE power saving enhancements | Huawei |
| R1-2112957 | Introduction of NR UE Power Saving Enhancements | Nokia |
| 8.7.1.1 | Potential paging enhancements | |
| R1-2110837 | Paging enhancements for UE power saving in IDLE/inactive mode | Huawei, HiSilicon |
| R1-2110937 | Discussion on power saving enhancements for paging | ZTE, Sanechips |
| R1-2111023 | Remaining issues on paging enhancements for idle/inactive mode UE power saving | vivo |
| R1-2111062 | Paging enhancements for idle/inactive UE power saving | TCL Communication Ltd. |
| R1-2111103 | Discussion on potential paging enhancements for UE power saving | Spreadtrum Communications |
| R1-2111266 | Paging enhancement for UE power saving | CATT |
| R1-2111325 | Further discussion on Paging enhancements for power saving | OPPO |
| R1-2111404 | Remaining issues on potential paging enhancement | Sony |
| R1-2111504 | On remaining aspects of paging early indication design | Intel Corporation |
| R1-2111582 | Paging enhancement for power saving | Xiaomi |
| R1-2111617 | Discussion on paging early indication design | CMCC |
| R1-2111674 | Discussion on PEI Design | Transsion Holdings |
| R1-2111675 | On paging enhancement | Panasonic |
| R1-2111747 | Discussion on paging enhancements | Samsung |
| R1-2111884 | Paging enhancements for idle/inactive-mode UE | Apple |
| R1-2111945 | Paging enhancement for UE power saving | Lenovo, Motorola Mobility |
| R1-2111960 | Discussion on paging enhancements for UE power saving | InterDigital, Inc. |
| R1-2112060 | Discussion on potential paging enhancements | LG Electronics |
| R1-2112116 | Discussion on paging enhancement | NTT DOCOMO, INC. |
| R1-2112149 | Design of Paging Enhancements | Ericsson |
| R1-2112226 | Paging enhancements for idle/inactive UE power saving | Qualcomm Incorporated |
| R1-2112307 | Summary #1 of paging enhancements | MediaTek Inc. |
| R1-2112308 | Remaining design details of paging early indication | MediaTek Inc. |
| R1-2112370 | Open items on paging enhancements for UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2112379 | On paging early indication | Nordic Semiconductor ASA |
| R1-2112662 | Summary#2 of paging enhancements | Moderator (MediaTek Inc.) |
| R1-2112886 | Summary#3 of paging enhancements | Moderator (MediaTek Inc.) |
| 8.7.1.2 | TRS/CSI-RS occasion(s) for idle/inactive UEs | |
| R1-2110838 | Assistance RS occasions for IDLE/inactive mode | Huawei, HiSilicon |
| R1-2110938 | TRS for RRC idle and inactive UEs | ZTE, Sanechips |
| R1-2111024 | Remaining issues on TRS/CSI-RS occasion(s) for idle/inactive UEs | vivo |
| R1-2111063 | TRS/CSI-RS occasions for IDLE/inactive mode | TCL Communication Ltd. |
| R1-2111104 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | Spreadtrum Communications |
| R1-2111267 | Configuration of TRS/CSI-RS for paging enhancement | CATT |
| R1-2111326 | Further discussion on RS occasion for idle/inactive UEs | OPPO |
| R1-2111405 | Remaining issues on TRS occasion(s) for idle/inactive UEs | Sony |
| R1-2111505 | Discussion on TRS occasions in idle/inactive mode | Intel Corporation |
| R1-2111583 | On TRS/CSI-RS configuration and indication for idle/inactive UEs | Xiaomi |
| R1-2111618 | Discussion on TRS/CSI-RS occasion(s) for IDLE/INACTIVE-mode UEs | CMCC |
| R1-2111676 | Potential enhancements for TRS/CSI-RS occasion(s) for idle/inactive UEs | Panasonic |
| R1-2111748 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | Samsung |
| R1-2111749 | Moderator Summary#1 on TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2111885 | Indication of TRS configurations for idle/inactive-mode UE power saving | Apple |
| R1-2111946 | Provision of TRS/CSI-RS for idle/inactive UEs | Lenovo, Motorola Mobility |
| R1-2111961 | Remaining issues on TRS/CSI-RS occasion(s) for idle/inactive UEs | InterDigital, Inc. |
| R1-2112018 | Discussion on TRS/CSI-RS occasions for idle/inactive UEs | Sharp |
| R1-2112061 | Discussion on TRS/CSI-RS occasion(s) for idle/inactive UEs | LG Electronics |
| R1-2112117 | Discussion on TRS/CSI-RS occasion for idle/inactive UEs | NTT DOCOMO, INC. |
| R1-2112150 | Provisioning TRS occasions to Idle/Inactive UEs | Ericsson |
| R1-2112227 | TRS/CSI-RS for idle/inactive UE power saving | Qualcomm Incorporated |
| R1-2112309 | On TRS/CSI-RS occasion(s) for idle/inactive mode UE power saving | MediaTek Inc. |
| R1-2112371 | Open issues on TRS information for IDLE/INACTIVE mode UEs | Nokia, Nokia Shanghai Bell |
| R1-2112380 | On TRS design for idle/inactive UEs | Nordic Semiconductor ASA |
| R1-2112682 | Moderator Summary #2 on TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| R1-2112683 | Moderator Summary #3 on TRS/CSI-RS occasion(s) for idle/inactive UEs | Moderator (Samsung) |
| 8.7.1.3 | Other | |
| R1-2110839 | Analysis on power consumption for IDLE mode UE | Huawei, HiSilicon |
| R1-2110939 | Additional simulation results of UE power consumption in RRC idle and inactive state | ZTE, Sanechips |
| R1-2111025 | Discussion on paging grouping | vivo |
| R1-2111268 | Multiple POs associated with one PEI | CATT |
| R1-2112151 | Modeling of NR gNB power consumption | Ericsson |
| R1-2112228 | Aligning Paging Occasions to SSB for UE idle and inactive mode power saving | Qualcomm Incorporated |
| 8.7.2 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | |
| R1-2110840 | Extensions to Rel-16 DCI-based power saving adaptation for an active BWP | Huawei, HiSilicon |
| R1-2110940 | Extension to Rel-16 DCI-based power saving adaptation during DRX Active Time | ZTE, Sanechips |
| R1-2111026 | Remaining issues on DCI-based power saving adaptation in connected mode | vivo |
| R1-2111105 | Discussion on power saving techniques for connected-mode UEs | Spreadtrum Communications |
| R1-2111181 | Discussion on DCI-based power saving adaptation | NEC |
| R1-2111269 | PDCCH monitoring adaptation | CATT |
| R1-2111327 | DCI-based power saving adaptation solutions | OPPO |
| R1-2111506 | Discussion on DCI-based power saving adaptation in active time | Intel Corporation |
| R1-2111619 | Discussion on PDCCH monitoring reduction during DRX active time | CMCC |
| R1-2111677 | Potential extension(s) to Rel-16 DCI-based power saving adaptation during DRX ActiveTime | Panasonic |
| R1-2111750 | Discussion on DCI-based power saving techniques | Samsung |
| R1-2111886 | Enhanced DCI-based power saving adaptation | Apple |
| R1-2111947 | Enhanced DCI based power saving adaptation | Lenovo, Motorola Mobility |
| R1-2111962 | DCI-based power saving adaptation during DRX Active Time | InterDigital, Inc. |
| R1-2111992 | Remaining issues on DCI-based power saving adaptation during DRX active time | ETRI |
| R1-2112062 | Discussion on DCI-based power saving adaptation during DRX ActiveTime | LG Electronics |
| R1-2112075 | Discussion on extension(s) to Rel-16 DCI-based power saving adaptation | FGI, Asia Pacific Telecom |
| R1-2112118 | Discussion on extension to DCI-based power saving adaptation | NTT DOCOMO, INC. |
| R1-2112152 | Design of active time power savings mechanisms | Ericsson |
| R1-2112229 | DCI-based power saving adaptation during DRX ActiveTime | Qualcomm Incorporated |
| R1-2112310 | On enhancements to DCI-based UE power saving during DRX active time | MediaTek Inc. |
| R1-2112372 | Open issues on PDCCH monitoring adaptation for UE power saving | Nokia, Nokia Shanghai Bell |
| R1-2112381 | On PDCCH monitoring adaptation | Nordic Semiconductor ASA |
| R1-2112397 | DCI-based Power Saving Enhancements | Fraunhofer HHI, Fraunhofer IIS |
| R1-2112578 | FL summary#1 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2112579 | FL summary#2 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2112769 | FL summary#3 of DCI-based power saving adaptation | Moderator (vivo) |
| R1-2112878 | Final FL summary of DCI-based power saving adaptation | Moderator (vivo) |
| 8.7.3 | Other | |
| R1-2110941 | Further discussion on potential power saving schemes for RRC connected UEs | ZTE, Sanechips |
| R1-2111270 | PDCCH skipping and SS group switching | CATT |
| R1-2111930 | Other considerations on power saving in Rel-17 | Huawei, HiSilicon |
| R1-2112153 | Evaluation results for UE power saving schemes | Ericsson |
| 8.8 | NR coverage enhancement | |
| R1-2111648 | Discussion on priorities for remaining issues for coverage enhancements | vivo |
| R1-2112433 | Introduction of coverage enhancements | Ericsson |
| R1-2112440 | Introduction of coverage enhancements in NR | Samsung |
| R1-2112470 | Introduction of Coverage Enhancements | Huawei |
| R1-2112480 | Introduction of NR coverage enhancements | Nokia |
| R1-2112795 | Session notes for 8.8 (NR coverage enhancement) | Ad-hoc Chair (CMCC) |
| R1-2112827 | [107-e-R17-RRC-CovEnh] Summary of email discussion on Rel-17 RRC parameters for Coverage Enhancement | Moderator (China Telecom, Sharp, Nokia, Qualcomm, ZTE) |
| R1-2112899 | RAN1 agreements for Rel-17 NR coverage enhancements | WI rapporteur (China Telecom) |
| R1-2112922 | Introduction of coverage enhancements | Ericsson |
| R1-2112928 | Introduction of coverage enhancements in NR | Samsung |
| R1-2112939 | Introduction of Coverage Enhancements | Huawei |
| R1-2112946 | Introduction of NR coverage enhancements | Nokia |
| 8.8.1.1 | Enhancements on PUSCH repetition type A | |
| R1-2110789 | Discussion on coverage enhancements for PUSCH repetition type A | Huawei, HiSilicon |
| R1-2110863 | Enhancements on PUSCH repetition type A | Nokia, Nokia Shanghai Bell |
| R1-2110918 | Discussion on enhanced PUSCH repetition type A | ZTE |
| R1-2111027 | Remaining issues on enhancement for PUSCH repetition type A | vivo |
| R1-2111106 | Discussion on enhancements for PUSCH repetition Type A | Spreadtrum Communications |
| R1-2111203 | Discussion on PUSCH repetition type A enhancements | TCL Communication Ltd. |
| R1-2111271 | Discussion on enhancements on PUSCH repetition type A | CATT |
| R1-2111328 | Enhancements on PUSCH repetition type A | OPPO |
| R1-2111426 | Remaining issues on PUSCH repetition type A enhancements | China Telecom |
| R1-2111437 | Discussion on enhancements on PUSCH repetition Type A | Panasonic Corporation |
| R1-2111507 | Enhancements on PUSCH repetition type A | Intel Corporation |
| R1-2111584 | Enhancements on PUSCH repetition type A | Xiaomi |
| R1-2111590 | Discussion on enhancements on PUSCH repetition type A | Rakuten Mobile, Inc |
| R1-2111620 | Discussion on enhancements on PUSCH repetition type A | CMCC |
| R1-2111751 | Enhancements on PUSCH repetition type A | Samsung |
| R1-2111792 | Type-A PUSCH repetition for coverage enhancement | InterDigital, Inc. |
| R1-2111842 | Design considerations for PUSCH repetition Type A Enhancements | Sierra Wireless. S.A. |
| R1-2111887 | Discussion on PUSCH repetition type A enhancement | Apple |
| R1-2111948 | Enhancements on PUSCH repetition type A | Lenovo, Motorola Mobility |
| R1-2112019 | Enhancements on PUSCH repetition type A | Sharp |
| R1-2112035 | Remaining Issues for PUSCH Repetition Type A Enhancement | Ericsson |
| R1-2112119 | Enhancements on PUSCH repetition type A | NTT DOCOMO, INC. |
| R1-2112230 | Enhancements on PUSCH Repetition Type A | Qualcomm Incorporated |
| R1-2112519 | FL Summary #1 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2112520 | FL Summary #2 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| R1-2112521 | FL Summary #3 on Enhancements on PUSCH repetition type A | Moderator (Sharp) |
| 8.8.1.2 | TB processing over multi-slot PUSCH | |
| R1-2110790 | Discussion on TB processing over multi-slot PUSCH | Huawei, HiSilicon |
| R1-2110864 | Transport block processing for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2110919 | Discussion on TB processing over multi-slot PUSCH | ZTE |
| R1-2111028 | Remaining issues on PUSCH TB processing over multiple slots | vivo |
| R1-2111107 | Discussion on TB processing over multi-slot PUSCH | Spreadtrum Communications |
| R1-2111149 | Views on TB processing over multi-slot PUSCH | Fujitsu |
| R1-2111204 | Discussion on TB processing over multi-slot PUSCH | TCL Communication Ltd. |
| R1-2111272 | Discussion on TB processing over multi-slot PUSCH | CATT |
| R1-2111329 | Further considerations for TB over multi-slot PUSCH | OPPO |
| R1-2111427 | Remaining issues on TB processing over multi-slot PUSCH | China Telecom |
| R1-2111438 | Discussion on TB processing over multi-slot PUSCH | Panasonic Corporation |
| R1-2111508 | Discussion on TB processing over multi-slot PUSCH | Intel Corporation |
| R1-2111585 | Discussion on TB processing over multi-slot PUSCH | Xiaomi |
| R1-2111621 | Discussion on TB processing over multi-slot PUSCH | CMCC |
| R1-2111693 | Discussion on TB processing over multi-slot PUSCH | NEC |
| R1-2111752 | TB processing over multi-slot PUSCH | Samsung |
| R1-2111793 | TB processing over multiple slots | InterDigital, Inc. |
| R1-2111888 | Discussion on TB processing over multi-slot PUSCH | Apple |
| R1-2111949 | Enhancements for TB processing over multi-slot PUSCH | Lenovo, Motorola Mobility |
| R1-2111979 | Discussions on TB processing over multi-slot PUSCH | LG Electronics |
| R1-2112020 | Transport block processing over multi-slot PUSCH | Sharp |
| R1-2112036 | Remaining Issues for TB Processing over Multi-Slot PUSCH | Ericsson |
| R1-2112120 | TB processing over multi-slot PUSCH | NTT DOCOMO, INC. |
| R1-2112231 | TB processing over multi-slot PUSCH | Qualcomm Incorporated |
| R1-2112316 | Discussion on TB processing over multi-slot | MediaTek Inc. |
| R1-2112390 | Discussion on TB processing over multi-slot PUSCH | WILUS Inc. |
| R1-2112462 | FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2112611 | Remaining Issues for TB Processing over Multi-Slot PUSCH | Ericsson |
| R1-2112686 | FL summary #2 of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2112687 | FL summary #3 of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| R1-2112688 | Final FL summary of TB processing over multi-slot PUSCH (AI 8.8.1.2) | Moderator (Nokia/Nokia Shanghai Bell) |
| 8.8.1.3 | Joint channel estimation for PUSCH | |
| R1-2110791 | Discussion on joint channel estimation for PUSCH | Huawei, HiSilicon |
| R1-2110865 | Joint channel estimation for PUSCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2110920 | Discussion on joint channel estimation for PUSCH | ZTE |
| R1-2111029 | Remaining issues on joint channel estimation for PUSCH | vivo |
| R1-2111108 | Discussion on joint channel estimation for PUSCH | Spreadtrum Communications |
| R1-2111205 | Discussion on joint channel estimation for PUSCH | TCL Communication Ltd. |
| R1-2111273 | Discussion on joint channel estimation for PUSCH | CATT |
| R1-2111330 | Consideration on Joint channel estimation for PUSCH | OPPO |
| R1-2111425 | Discussion on joint channel estimation for PUSCH | Panasonic Corporation |
| R1-2111428 | Remaining issues on joint channel estimation for PUSCH | China Telecom |
| R1-2111429 | FL Summary of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2111509 | Discussion on joint channel estimation for PUSCH | Intel Corporation |
| R1-2111586 | Discussion on joint channel estimation for PUSCH | Xiaomi |
| R1-2111622 | Discussion on joint channel estimation for PUSCH | CMCC |
| R1-2111681 | On events for Joint Channel Estimation for PUSCH | Sony |
| R1-2111753 | Joint channel estimation for PUSCH | Samsung |
| R1-2111794 | Joint channel estimation for PUSCH | InterDigital, Inc. |
| R1-2111841 | Design Considerations for Joint channel estimation for PUSCH | Sierra Wireless. S.A. |
| R1-2111889 | Discussion on joint channel estimation for PUSCH | Apple |
| R1-2111950 | Enhancements for joint channel estimation for multiple PUSCH | Lenovo, Motorola Mobility |
| R1-2111980 | Discussions on joint channel estimation for PUSCH | LG Electronics |
| R1-2112021 | Joint channel estimation for multiple PUSCH transmission | Sharp |
| R1-2112037 | Remaining Issues for Joint Channel Estimation for PUSCH | Ericsson |
| R1-2112121 | Joint channel estimation for PUSCH | NTT DOCOMO, INC. |
| R1-2112232 | Joint channel estimation for PUSCH | Qualcomm Incorporated |
| R1-2112317 | Discussion on Joint channel estimation over multi-slot | MediaTek Inc. |
| R1-2112391 | Discussion on joint channel estimation for PUSCH | WILUS Inc. |
| R1-2112561 | FL Summary#2 of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2112562 | FL Summary#3 of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2112563 | FL Summary#4 of joint channel estimation for PUSCH | Moderator (China Telecom) |
| R1-2112828 | [107-e-NR-R17-CovEnh-03] Summary of email discussion on joint channel estimation for PUSCH | Moderator (China Telecom) |
| 8.8.2 | PUCCH enhancements | |
| R1-2110792 | Discussion on PUCCH coverage enhancement | Huawei, HiSilicon |
| R1-2110866 | PUCCH coverage enhancements | Nokia, Nokia Shanghai Bell |
| R1-2110921 | Discussion on coverage enhancements for PUCCH | ZTE |
| R1-2111030 | Remaining issues on PUCCH enhancements | vivo |
| R1-2111109 | Discussion on PUCCH enhancements | Spreadtrum Communications |
| R1-2111274 | Discussion on PUCCH enhancement | CATT |
| R1-2111331 | PUCCH enhancements for coverage | OPPO |
| R1-2111430 | Remaining issues on PUCCH enhancements | China Telecom |
| R1-2111439 | Discussion on PUCCH enhancement for NR coverage enhancement | Panasonic Corporation |
| R1-2111510 | Discussion on PUCCH enhancements | Intel Corporation |
| R1-2111587 | Discussion on PUCCH enhancements | Xiaomi |
| R1-2111623 | Discussion on PUCCH enhancements | CMCC |
| R1-2111694 | Discussion on dynamic PUCCH repetition factor | NEC |
| R1-2111754 | PUCCH enhancements | Samsung |
| R1-2111795 | Discussions on PUCCH enhancements | InterDigital, Inc. |
| R1-2111890 | PUCCH coverage enhancement | Apple |
| R1-2111951 | Enhancements for PUCCH repetition | Lenovo, Motorola Mobility |
| R1-2111981 | Discussions on coverage enhancement for PUCCH | LG Electronics |
| R1-2111993 | PUCCH enhancements | ETRI |
| R1-2112022 | PUCCH coverage enhancement | Sharp |
| R1-2112038 | Remaining Issues for PUCCH Dynamic Repetition and DMRS Bundling | Ericsson |
| R1-2112122 | PUCCH enhancements for coverage enhancement | NTT DOCOMO, INC. |
| R1-2112233 | PUCCH enhancements | Qualcomm Incorporated |
| R1-2112392 | Discussion on PUCCH enhancements for coverage enhancement | WILUS Inc. |
| R1-2112582 | FL summary #1 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| R1-2112622 | FL summary #2 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| R1-2112700 | FL summary #3 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| R1-2112708 | FL summary #4 of PUCCH coverage enhancement | Moderator (Qualcomm) |
| 8.8.3 | Type A PUSCH repetitions for Msg3 | |
| R1-2110793 | Discussion on Msg3 repetition for coverage enhancement | Huawei, HiSilicon |
| R1-2110867 | Approaches and solutions for Type A PUSCH repetitions for Msg3 | Nokia, Nokia Shanghai Bell |
| R1-2110922 | Discussion on support of Type A PUSCH repetitions for Msg3 | ZTE |
| R1-2111031 | Remaining issues on Type A PUSCH repetitions for Msg3 | vivo |
| R1-2111110 | Discussion on Type A PUSCH repetitions for Msg3 | Spreadtrum Communications |
| R1-2111275 | Discussion on Type A PUSCH repetitions for Msg3 | CATT |
| R1-2111332 | Type A PUSCH repetitions for Msg3 coverage | OPPO |
| R1-2111431 | Remaining issues on type A PUSCH repetitions for Msg3 | China Telecom |
| R1-2111440 | Discussion on Type A PUSCH repetitions for Msg.3 | Panasonic Corporation |
| R1-2111511 | On Msg3 PUSCH repetition | Intel Corporation |
| R1-2111588 | Discussion on Type A PUSCH repetition for Msg3 | Xiaomi |
| R1-2111624 | Discussion on type A PUSCH repetitions for Msg3 | CMCC |
| R1-2111755 | Type A PUSCH repetitions for Msg3 | Samsung |
| R1-2111796 | Type A PUSCH repetitions for Msg3 | InterDigital, Inc. |
| R1-2111891 | Discussion on Msg3 Coverage Enhancement | Apple |
| R1-2111982 | Discussion on coverage enhancement for Msg3 PUSCH | LG Electronics |
| R1-2111994 | Type A PUSCH repetitions for Msg3 | ETRI |
| R1-2112023 | Type A PUSCH repetitions for Msg3 | Sharp |
| R1-2112039 | Remaining Issues for Type A PUSCH Repetition for Msg3 | Ericsson |
| R1-2112123 | Type A PUSCH repetitions for Msg3 | NTT DOCOMO, INC. |
| R1-2112234 | Type A PUSCH repetition for Msg3 | Qualcomm Incorporated |
| R1-2112393 | Discussion on Type A PUSCH repetitions for Msg3 | WILUS Inc. |
| R1-2112543 | Discussion on Msg3 repetition for coverage enhancement | Huawei, HiSilicon |
| R1-2112556 | Feature lead summary #1 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2112557 | Feature lead summary #2 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2112558 | Feature lead summary #3 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| R1-2112836 | Feature lead summary #4 on support of Type A PUSCH repetitions for Msg3 | Moderator (ZTE) |
| 8.8.4 | Other | |
| R1-2110868 | Discussion on the dependency of RRC parameters for counting on available slots and TBoMS | Nokia, Nokia Shanghai Bell |
| R1-2110923 | Discussion on RRC parameters for coverage enhancement | ZTE |
| R1-2111032 | Enhanced contention resolution mechanism for CBRA procedure with MSG3 PUSCH repetition | vivo |
| R1-2111589 | Other considerations for coverage enhancement | xiaomi |
| R1-2112040 | Frequency Hopping for TBoMS | Ericsson |
| R1-2112401 | On futher potential coverage enhancements | Huawei, HiSilicon |
| 8.9 | Rel-17 enhancements for NB-IoT and LTE-MTC | |
| R1-2112417 | Introduction of Additional Enhancements for NB-IoT and LTE-MTC in 36.213 s06-07 | Motorola Mobility |
| R1-2112418 | Introduction of Additional Enhancements for NB-IoT and LTE-MTC in 36.213 s10-s13 | Motorola Mobility |
| R1-2112419 | Introduction of Additional Enhancements for NB-IoT and LTE-MTC in 36.213 s14-xx | Motorola Mobility |
| R1-2112434 | Introduction of additional enhancements for NB-IoT and LTE-MTC | Ericsson |
| R1-2112496 | Introduction of Rel-17 NB-IoT and eMTC features | FUTUREWEI |
| R1-2112796 | Session notes for 8.9 (Rel-17 enhancements for NB-IoT and LTE-MTC) | Ad-hoc Chair (CMCC) |
| R1-2112877 | Feature lead summary on 107-e-R17-RRC-NB-IoT-eMTC | Moderator (Huawei) |
| R1-2112897 | RAN1 agreements of Additional enhancements for NB-IoT and LTE-MTC | WI rapporteur (Huawei) |
| R1-2112906 | Introduction of Additional Enhancements for NB-IoT and LTE-MTC in 36.213 s06-07 | Motorola Mobility |
| R1-2112907 | Introduction of Additional Enhancements for NB-IoT and LTE-MTC in 36.213 s10-s13 | Motorola Mobility |
| R1-2112908 | Introduction of Additional Enhancements for NB-IoT and LTE-MTC in 36.213 s14-xx | Motorola Mobility |
| R1-2112923 | Introduction of additional enhancements for NB-IoT and LTE-MTC | Ericsson |
| R1-2112958 | Introduction of Rel-17 NB-IoT and eMTC features | FUTUREWEI |
| 8.9.1 | Support of 16-QAM for unicast in UL and DL for NB-IoT | |
| R1-2110857 | Support of 16QAM for unicast in UL and DL in NB-IoT | Huawei, HiSilicon |
| R1-2111070 | Discussion on 16QAM for NB-IoT | ZTE, Sanechips |
| R1-2111133 | Support of 16-QAM for NB-IoT | Nokia, Nokia Shanghai Bell |
| R1-2111449 | Support of 16-QAM for NB-IoT | Qualcomm Incorporated |
| R1-2112001 | Support 16QAM for NBIoT | Lenovo, Motorola Mobility |
| R1-2112300 | Discussion on CQI table and NPUSCH power control parameter for 16QAM | MediaTek Inc. |
| R1-2112361 | Support of 16-QAM for unicast in UL and DL in NB-IoT | Ericsson |
| R1-2112576 | Feature lead summary #1 on 107-e-LTE-Rel17-NB-IoT-eMTC-01 | Moderator (Huawei) |
| R1-2112651 | Feature lead summary #2 on 107-e-LTE-Rel17-NB-IoT-eMTC-01 | Moderator (Huawei) |
| R1-2112747 | Feature lead summary #3 on 107-e-LTE-Rel17-NB-IoT-eMTC-01 | Moderator (Huawei) |
| R1-2112970 | Draft LS on channel quality reporting for NB-IoT | Moderator (Huawei) |
| R1-2112971 | LS on channel quality reporting for NB-IoT | RAN1, Huawei |
| 8.9.2 | Support additional PDSCH scheduling delay for introduction of 14-HARQ processes in DL for eMTC | |
| R1-2110858 | Support of 14-HARQ processes in DL for HD-FDD MTC UEs | Huawei, HiSilicon |
| R1-2111071 | Remaining issues on 14-HARQ processes in DL for eMTC | ZTE, Sanechips |
| R1-2111134 | Support of 14-HARQ processes in DL for eMTC | Nokia, Nokia Shanghai Bell |
| R1-2111450 | Support of 14 HARQ processes and scheduling delay | Qualcomm Incorporated |
| R1-2112362 | Support of 14 HARQ processes in DL in LTE-MTC | Ericsson |
| R1-2112517 | Summary#1st check point [107-e-LTE-Rel17-NB-IoT-eMTC-02] on support additional PDSCH scheduling delay for introduction of 14-HARQ processes in DL for eMTC | Moderator (Ericsson) |
| R1-2112518 | Final summary [107-e-LTE-Rel17-NB-IoT-eMTC-02] on support additional PDSCH scheduling delay for introduction of 14-HARQ processes in DL for eMTC | Moderator (Ericsson) |
| 8.9.3 | Other | |
| R1-2111939 | Further considerations on Rel-17 NB-IoT and eMTC enhancements | Huawei, HiSilicon |
| R1-2112363 | On the support of 16-QAM for unicast in UL and DL in TDD NB-IoT | Ericsson |
| 8.10 | Enhancements to Integrated Access and Backhaul | |
| R1-2112442 | Introduction of R17 eIAB | Samsung |
| R1-2112838 | Summary of [107-e-R17-RRC-eIAB] on Rel-17 higher layer parameters (RRC, MAC-CE, and F1AP) for eIAB | Moderator (Qualcomm) |
| R1-2112930 | Introduction of R17 eIAB | Samsung |
| R1-2112965 | RAN1 decisions for Rel-17 eIAB | WI rapporteur (Qualcomm) |
| R1-2112966 | Summary of [107-e-R17-RRC-eIAB] on Rel-17 higher layer parameters (RRC, MAC-CE, and F1AP) for eIAB | Moderator (Qualcomm) |
| 8.10.1 | Enhancements to resource multiplexing between child and parent links of an IAB node | |
| R1-2110775 | Enhancements for resource multiplexing among IAB backhaul and access links | Nokia, Nokia Shanghai Bell |
| R1-2110834 | Resource multiplexing between backhaul and access for IAB duplexing enhancements | Huawei, HiSilicon |
| R1-2111033 | Remaining issues on enhancement to resource multiplexing between child and parent links | vivo |
| R1-2111512 | Enhancements to Resource Multiplexing between Child and Parent Links of an IAB Node | Intel Corporation |
| R1-2111591 | Enhancements to the IAB resource multiplexing | ZTE, Sanechips |
| R1-2111756 | Enhancements to Resource Multiplexing for NR IAB | Samsung |
| R1-2111804 | Enhancements for IAB resource multiplexing | AT&T |
| R1-2111892 | Enhanced resource multiplexing within and across IAB nodes | Apple |
| R1-2111952 | Resource multiplexing in enhanced IAB systems | Lenovo, Motorola Mobility |
| R1-2111983 | Discussions on IAB resource multiplexing enhancements | LG Electronics |
| R1-2111995 | Discussion on IAB resource multiplexing enhancements | ETRI |
| R1-2112124 | Resource multiplexing between child and parent links of an IAB node | NTT DOCOMO, INC. |
| R1-2112183 | Discussions on enhancements to resource multiplexing between child and parent links of an IAB node | CEWiT |
| R1-2112235 | Resource management for enhanced duplexing | Qualcomm Incorporated |
| R1-2112356 | Resource multiplexing in enhanced IAB | Ericsson |
| R1-2112602 | Feature lead summary #1 of 8.10.1 | Moderator (AT&T) |
| R1-2112603 | Feature lead summary #2 of 8.10.1 | Moderator (AT&T) |
| R1-2112804 | Feature lead summary #3 of 8.10.1 | Moderator (AT&T) |
| 8.10.2 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | |
| R1-2110776 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | Nokia, Nokia Shanghai Bell |
| R1-2110835 | Enhancements for simultaneous operation of MT and DU | Huawei, HiSilicon |
| R1-2111034 | Remaining issues on enhancements for simultaneous operation of child and parent links | vivo |
| R1-2111513 | Support for Case#6 and Case#7 Timing Alignment | Intel Corporation |
| R1-2111592 | Enhancements for simultaneous operation of child and parent links | ZTE, Sanechips |
| R1-2111757 | Enhancements to Timing, Power Control and CLI for NR IAB | Samsung |
| R1-2111805 | Enhancements for IAB interference management | AT&T |
| R1-2111893 | Other enhancements for simultaneous operation of an IAB node's links | Apple |
| R1-2111953 | Timing, interference, and power control in enhanced IAB systems | Lenovo, Motorola Mobility |
| R1-2111984 | Discussions on other enhancement for simultaneous operation | LG Electronics |
| R1-2111996 | Discussion on simultaneous operation enhancements for eIAB | ETRI |
| R1-2112125 | Other enhancements for simultaneous operation of IAB-node’s child and parent links | NTT DOCOMO, INC. |
| R1-2112236 | Enhancements for simultaneous operation of IAB-node's child and parent links | Qualcomm Incorporated |
| R1-2112267 | Discussion on simultaneous operation of IAB-node’s child and parent links | CEWiT |
| R1-2112357 | Timing and power control in enhanced IAB | Ericsson |
| R1-2112636 | Summary#1 for [107-e-NR-eIAB-02] on other enhancements for simultaneous operation of IAB-node's child and parent links | Moderator (Qualcomm) |
| R1-2112837 | Final summary for [107-e-NR-eIAB-02] on other enhancements for simultaneous operation of IAB-node's child and parent links | Moderator (Qualcomm) |
| R1-2112972 | [DRAFT] LS on range of power control parameters for eIAB | Moderator (Qualcomm) |
| R1-2112973 | LS on range of power control parameters for eIAB | RAN1, Qualcomm |
| 8.10.3 | Other | |
| R1-2111035 | Other enhancements to Rel-17 IAB nodes | vivo |
| R1-2111593 | Consideration on reference carrier for semi-static IAB-DU resource configuration | ZTE, Sanechips |
| R1-2111929 | Other enhancements for IAB | Huawei, HiSilicon |
| R1-2112358 | Prioritization of remaining work in eIAB | Ericsson |
| 8.11 | NR Sidelink enhancement | |
| R1-2112490 | Introduction of NR Sidelink enhancements | Nokia |
| R1-2112650 | [107-e-R17-RRC-Sidelink] Summary of email discussion on Rel-17 RRC parameters for sidelink enhancement | Moderator (LG Electronics) |
| R1-2112956 | Introduction of NR Sidelink enhancements | Nokia |
| R1-2112963 | Introduction of NR sidelink enhancement | Huawei |
| R1-2112988 | Introduction of sidelink enhancements in NR | Samsung |
| R1-2112989 | Introduction of Rel-17 sidelink enhancements | Huawei |
| 8.11.1 | Resource allocation enhancement | |
| R1-2112167 | Candidate resource selection for SL DRX | ITL |
| 8.11.1.1 | Resource allocation for power saving | |
| R1-2110844 | Sidelink resource allocation to reduce power consumption | Huawei, HiSilicon |
| R1-2110861 | Resource allocation for power saving | Nokia, Nokia Shanghai Bell |
| R1-2110886 | Power consumption reduction for sidelink resource allocation | FUTUREWEI |
| R1-2111036 | Remaining issues on resource allocation for sidelink power saving | vivo |
| R1-2111111 | Discussion on sidelink resource allocation for power saving | Spreadtrum Communications |
| R1-2111121 | Discussion on Sidelink Resource Allocation for Power Saving | Panasonic Corporation |
| R1-2111150 | Considerations on partial sensing and DRX in NR Sidelink | Fujitsu |
| R1-2111228 | Remaining issues on sidelink resource allocation enhancements for power saving | CATT, GOHIGH |
| R1-2111300 | Discussion on power saving in NR sidelink communication | OPPO |
| R1-2111406 | Discussion on sidelink resource allocation for power saving | Sony |
| R1-2111514 | Remaining Details of Sidelink Resource Allocation Schemes for UE Power Saving | Intel Corporation |
| R1-2111546 | Discussion on sidelink resource allocation enhancement for power saving | Xiaomi |
| R1-2111625 | Discussion on resource allocation for power saving | CMCC |
| R1-2111637 | Discussion on resource allocation for power saving | ZTE, Sanechips |
| R1-2111649 | NR Sidelink Resource Allocation for UE Power Saving | Fraunhofer HHI, Fraunhofer IIS |
| R1-2111656 | Considerations on partial sensing mechanism of NR V2X | CAICT |
| R1-2111699 | Discussion on resource allocation for power saving | NEC |
| R1-2111758 | On Resource Allocation for Power Saving | Samsung |
| R1-2111815 | Discussion on resource allocation for power saving | LG Electronics |
| R1-2111824 | Sidelink resource allocation for power saving | InterDigital, Inc. |
| R1-2111894 | Sidelink Resource Allocation for Power Saving | Apple |
| R1-2111997 | Discussion on resource allocation for power saving | ETRI |
| R1-2112024 | Discussion on resource allocation for power saving | Sharp |
| R1-2112033 | On NR Resource Allocation for Power Saving | Convida Wireless |
| R1-2112042 | Discussion on partial sensing and SL DRX impact | ASUSTeK |
| R1-2112126 | Discussion on sidelink resource allocation for power saving | NTT DOCOMO, INC. |
| R1-2112164 | Sidelink resource allocation for power saving | Lenovo, Motorola Mobility |
| R1-2112237 | Power Savings for Sidelink | Qualcomm Incorporated |
| R1-2112305 | Remaining details on sidelink power saving | MediaTek Inc. |
| R1-2112336 | Resource allocation for power saving in NR sidelink enhancement | ITL |
| R1-2112351 | Resource allocation procedures for power saving | Ericsson |
| R1-2112394 | Discussion on sidelink enhancements for power saving | ROBERT BOSCH GmbH |
| R1-2112524 | FL summary for AI 8.11.1.1 – resource allocation for power saving (before 1st GTW) | Moderator (OPPO) |
| R1-2112525 | FL summary for AI 8.11.1.1 – resource allocation for power saving (before 2nd GTW) | Moderator (OPPO) |
| R1-2112526 | FL summary for AI 8.11.1.1 – resource allocation for power saving (before 3rd GTW) | Moderator (OPPO) |
| R1-2112527 | FL summary for AI 8.11.1.1 – resource allocation for power saving (before 4th GTW) | Moderator (OPPO) |
| R1-2112528 | FL summary for AI 8.11.1.1 – resource allocation for power saving (EOM) | Moderator (OPPO) |
| 8.11.1.2 | Inter-UE coordination for Mode 2 enhancements | |
| R1-2110845 | Inter-UE coordination in sidelink resource allocation | Huawei, HiSilicon |
| R1-2110862 | Inter-UE coordination for Mode 2 enhancements | Nokia, Nokia Shanghai Bell |
| R1-2110887 | Discussion on techniques for inter-UE coordination | FUTUREWEI |
| R1-2111037 | Remaining issues on mode-2 enhancements | vivo |
| R1-2111112 | Discussion on inter-UE coordination in sidelink resource allocation | Spreadtrum Communications |
| R1-2111151 | Considerations on inter-UE coordination for mode 2 enhancements | Fujitsu |
| R1-2111229 | Remaining issues on Inter-UE coordination for Mode 2 enhancements | CATT, GOHIGH |
| R1-2111301 | Inter-UE coordination in mode 2 of NR sidelink | OPPO |
| R1-2111354 | Inter-UE coordination for mode 2 enhancements | Zhejiang Lab |
| R1-2111407 | Discussion on inter-UE coordination for Mode 2 enhancements | Sony |
| R1-2111515 | Design of Inter-UE Coordination Solutions for Sidelink Communication | Intel Corporation |
| R1-2111547 | Discussion on inter-UE coordination | Xiaomi |
| R1-2111626 | Discussion on inter-UE coordination for mode 2 enhancement | CMCC |
| R1-2111650 | Resource Allocation Enhancements for Mode 2 | Fraunhofer HHI, Fraunhofer IIS |
| R1-2111657 | Considerations on mode 2 enhancements | CAICT |
| R1-2111667 | Discussion on inter-UE coordination | ZTE |
| R1-2111700 | Discussion on mode 2 enhencements | NEC |
| R1-2111759 | On Inter-UE Coordination for Mode2 Enhancements | Samsung |
| R1-2111816 | Discussion on inter-UE coordination for Mode 2 enhancements | LG Electronics |
| R1-2111817 | Feature lead summary #1 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2111818 | Feature lead summary #2 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2111819 | Feature lead summary #3 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2111825 | On inter-UE coordination for Mode 2 enhancement | InterDigital, Inc. |
| R1-2111827 | Inter-UE coordination for enhanced resource allocation | Mitsubishi Electric RCE |
| R1-2111895 | Inter-UE Coordination | Apple |
| R1-2111967 | Inter-UE coordination for Mode 2 enhancements | Panasonic Corporation |
| R1-2111998 | Discussion on inter-UE coordination for Mode 2 enhancements | ETRI |
| R1-2112025 | Discussion on inter-UE coordination for mode 2 enhancements | Sharp |
| R1-2112034 | Inter-UE Coordination for NR SL Mode 2 Enhancement | Convida Wireless |
| R1-2112043 | Discussion on V2X mode 2 enhancements | ASUSTeK |
| R1-2112127 | Resource allocation for reliability and latency enhancements | NTT DOCOMO, INC. |
| R1-2112165 | Inter-UE coordination for Mode 2 enhancements | Lenovo, Motorola Mobility |
| R1-2112238 | Reliability and Latency Enhancements for Mode 2 | Qualcomm Incorporated |
| R1-2112318 | Discussion on Mode 2 enhancements | MediaTek Inc. |
| R1-2112352 | Details on mode 2 enhancements for inter-UE coordination | Ericsson |
| R1-2112396 | Remaining details on mode 2 inter-UE coordination | ROBERT BOSCH GmbH |
| R1-2112577 | Reliability and Latency Enhancements for Mode 2 | Qualcomm Incorporated |
| R1-2112649 | Feature lead summary #4 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| R1-2112756 | Feature lead summary #5 for AI 8.11.1.2 Inter-UE coordination for Mode 2 enhancements | Moderator (LG Electronics) |
| 8.11.2 | Other | |
| R1-2111038 | Other aspects on SL enhancements | vivo |
| R1-2111548 | Discussion on other design aspects for sidelink enhancement | Xiaomi |
| R1-2111639 | Other enhancements on power saving | ZTE, Sanechips |
| R1-2111760 | Discussion on Sidelink Enhancement | Samsung |
| R1-2111826 | On gNB-designated resources for inter-UE coordination and sensing in SL DRX | InterDigital, Inc. |
| R1-2111896 | Network Assisted Resource Selection | Apple |
| R1-2111931 | Physical layer impacts of sidelink DRX | Huawei, HiSilicon |
| R1-2112353 | Additional considerations on resource allocation for power saving and inter-UE coordination | Ericsson |
| 8.12 | NR Multicast and Broadcast Services | |
| R1-2112435 | Introduction of support for multicast and broadcast services | Ericsson |
| R1-2112445 | Introduction of multicast-broadcast services in NR | Samsung |
| R1-2112471 | Introduction of NR Multicast and Broadcast Services | Huawei |
| R1-2112485 | Introduction of NR Multicast and Broadcast Services | Nokia |
| R1-2112515 | Introduction of multicast and broadcast services | Qualcomm |
| R1-2112797 | Session notes for 8.12 (NR Multicast and Broadcast Services) | Ad-Hoc Chair (Huawei) |
| R1-2112869 | Summary of email discussion on Rel-17 RRC parameters for NR MBS | Moderator (CMCC, Huawei, BBC) |
| R1-2112892 | Agreements for NR MBS up to RAN1#107 | WI rapporteur (CMCC) |
| R1-2112924 | Introduction of support for multicast and broadcast services | Ericsson |
| R1-2112933 | Introduction of multicast-broadcast services in NR | Samsung |
| R1-2112940 | Introduction of NR Multicast and Broadcast Services | Huawei |
| R1-2112951 | Introduction of NR Multicast and Broadcast Services | Nokia |
| R1-2112960 | Introduction of multicast and broadcast services | Qualcomm |
| R1-2112969 | Summary of email discussion on Rel-17 RRC parameters for NR MBS | Moderator (CMCC, Huawei, BBC) |
| R1-2112990 | Agreements for NR MBS up to RAN1#107bis | Rapporteur (CMCC) |
| 8.12.1 | Mechanisms to support group scheduling for RRC_CONNECTED UEs | |
| R1-2110777 | Resource configuration and group scheduling for RRC_CONNECTED UEs | Huawei, HiSilicon, CBN |
| R1-2110889 | Remaining Issues on MBS for Connected UEs | FUTUREWEI |
| R1-2110895 | Further discussion on group scheduling for multicast mode | TD Tech, Chengdu TD Tech |
| R1-2110910 | Discussion on Mechanisms to Support Group Scheduling for RRC_CONNECTED UEs | ZTE |
| R1-2111039 | Remaining issues on mechanisms to support group scheduling for RRC_CONNECTED Ues | vivo |
| R1-2111113 | Discussion on MBS group scheduling for RRC_CONNETED UEs | Spreadtrum Communications |
| R1-2111135 | Group Scheduling Mechanisms to Support 5G Multicast / Broadcast Services for RRC_CONNECTED UEs | Nokia, Nokia Shanghai Bell |
| R1-2111230 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2111303 | Discussion on group Scheduling mechanism for RRC_CONNECTED UEs | OPPO |
| R1-2111516 | NR-MBS Group Scheduling for RRC_CONNECTED UEs | Intel Corporation |
| R1-2111549 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | Xiaomi |
| R1-2111627 | Discussion on group scheduling mechanisms | CMCC |
| R1-2111630 | Summary#1 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2111695 | Discussion on Group Scheduling Mechanisms for RRC_CONNECTED UEs | NEC |
| R1-2111761 | Support of group scheduling for RRC_CONNECTED UEs | Samsung |
| R1-2111897 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | Apple |
| R1-2112063 | Support of group scheduling for RRC_CONNECTED UEs | LG Electronics |
| R1-2112080 | Discussion on mechanisms to support group scheduling for RRC_CONNECTED UEs | ASUSTeK |
| R1-2112128 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | NTT DOCOMO, INC. |
| R1-2112161 | On group scheduling mechanism for RRC_CONNECTED UEs | Lenovo, Motorola Mobility |
| R1-2112239 | Views on group scheduling for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2112312 | Discussion on NR MBS group scheduling for RRC_CONNECTED UEs | MediaTek Inc. |
| R1-2112346 | Mechanisms to support MBS group scheduling for RRC_CONNECTED Ues | Ericsson |
| R1-2112382 | Discussion on group scheduling mechanism for RRC_CONNECTED UEs | Google Inc. |
| R1-2112540 | Summary#2 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2112541 | Summary#3 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2112542 | Summary#4 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2112830 | Summary#5 on mechanisms to support group scheduling for RRC_CONNECTED UEs for NR MBS | Moderator (CMCC) |
| R1-2112851 | LS on multicast reception on SCell for MBS | RAN1, CMCC |
| 8.12.2 | Mechanisms to improve reliability for RRC_CONNECTED UEs | |
| R1-2110778 | Mechanisms to improve reliability for RRC_CONNECTED UEs | Huawei, HiSilicon, CBN |
| R1-2110890 | Remaining Issues on MBS Reliability | FUTUREWEI |
| R1-2110896 | PUCCH formats for NACK-ONLY based HARQ-ACK feedback | TD Tech, Chengdu TD Tech |
| R1-2110911 | Discussion on Mechanisms to Improve Reliability for RRC_CONNECTED UEs | ZTE |
| R1-2111040 | Remaining issues on mechanisms to improve reliability for RRC_CONNECTED Ues | vivo |
| R1-2111114 | Mechanisms to improve MBS reliability for RRC_CONNECTED UEs | Spreadtrum Communications |
| R1-2111136 | Reliability Improvements for RRC_CONNECTED UEs | Nokia, Nokia Shanghai Bell |
| R1-2111231 | Discussion on reliability improvement mechanism for RRC_CONNECTED UEs in MBS | CATT |
| R1-2111304 | UL feedback for RRC-CONNECTED UEs in MBS | OPPO |
| R1-2111472 | Discussion on enabling/disabling HARQ-ACK feedback for multicast of RRC_CONNECTED UEs | ETRI |
| R1-2111517 | Mechanisms to Improve Reliability of NR-MBS for RRC_CONNECTED UEs | Intel Corporation |
| R1-2111550 | Discussion on mechanisms to improve reliability for RRC_CONNECTED UEs | Xiaomi |
| R1-2111628 | Discussion on reliability improvement | CMCC |
| R1-2111696 | Discussion on Reliability Improvements for RRC_CONNECTED UEs | NEC |
| R1-2111762 | On mechanisms to improve reliability for RRC_CONNECTED UEs | Samsung |
| R1-2111898 | Discussion on MBS reliability improvement for RRC_CONNECTED UEs | Apple |
| R1-2111985 | Discussion on Reliability Enhancement for Simultaneous MBS and Unicast Reception | TCL Communication Ltd. |
| R1-2112064 | Mechanisms to improve reliability of Broadcast/Multicast service | LG Electronics |
| R1-2112129 | Discussion on HARQ-ACK feedback for multicast for RRC_CONNECTED UEs | NTT DOCOMO, INC. |
| R1-2112162 | On reliability improvement for RRC-CONNECTED UEs | Lenovo, Motorola Mobility |
| R1-2112240 | Views on UE feedback for Multicast RRC_CONNECTED UEs | Qualcomm Incorporated |
| R1-2112313 | Discussion on mechanisms to improve reliability for RRC_CONNECTED UEs | MediaTek Inc. |
| R1-2112347 | Mechanisms to improve reliability for RRC_CONNECTED Ues | Ericsson |
| R1-2112383 | Discussion on MBS reliability for RRC_CONNECTED UEs | Google Inc. |
| R1-2112456 | FL summary#1 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2112590 | FL summary#2 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2112591 | FL summary#3 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| R1-2112592 | FL summary#4 on improving reliability for MBS for RRC_CONNECTED UEs | Moderator (Huawei) |
| 8.12.3 | Basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | |
| R1-2110779 | Discussion on UE receiving broadcast in RRC IDLE/INACTIVE state | Huawei, HiSilicon, CBN |
| R1-2110891 | MBS Support for RRC IDLE/INACTIVE UEs | FUTUREWEI |
| R1-2110897 | Discussion on basic functions for broadcast mode | TD Tech, Chengdu TD Tech |
| R1-2110912 | Discussion on basic Functions for Broadcast or Multicast for RRC_IDLE or RRC_INACTIVE UEs | ZTE |
| R1-2111041 | Remaining issues on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE Ues | vivo |
| R1-2111115 | Basic Functions for Broadcast or Multicast for RRC_IDLE or RRC_INACTIVE UEs | Spreadtrum Communications |
| R1-2111137 | Basic Functions for Broadcast / Multicast for RRC_IDLE / RRC_INACTIVE UEs | Nokia, Nokia Shanghai Bell |
| R1-2111232 | Discussion on basic functions for broadcast multicast for RRC_IDLE RRC_INACTIVE UEs | CATT |
| R1-2111305 | Discussion on basic functions for RRC_IDLE/RRC_INACTIVE UEs | OPPO |
| R1-2111408 | Considerations on MBS functions for RRC_IDLE/INACTIVE UEs | Sony |
| R1-2111518 | NR-MBS for RRC_IDLE/INACTIVE UEs | Intel Corporation |
| R1-2111551 | Discussion on basic functions for broadcast/multicast for RRC_IDLERRC_INACTIVE UEs | Xiaomi |
| R1-2111629 | Discussion on NR MBS in RRC_IDLE/ RRC_INACTIVE states | CMCC |
| R1-2111763 | On basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | Samsung |
| R1-2111899 | Discussion on MBS for RRC_IDLE and RRC_INACTIVE UEs | Apple |
| R1-2112065 | Basic function for broadcast/multicast | LG Electronics |
| R1-2112082 | Discussion on basic functions for broadcast or multicast for RRC_IDLE and RRC_INACTIVE UEs | ASUSTeK |
| R1-2112130 | Discussion on basic functions for broadcast/multicast for RRC_IDLE/RRC_INACTIVE UEs | NTT DOCOMO, INC. |
| R1-2112163 | Basic functions for broadcast/multicast in idle/inactive states | Lenovo, Motorola Mobility |
| R1-2112241 | Views on group scheduling for Broadcast RRC_IDLE/INACTIVE UEs | Qualcomm Incorporated |
| R1-2112314 | Discussion on MBS for RRC_IDLE and INACTIVE UEs | MediaTek Inc. |
| R1-2112348 | Support for NR multicast reception in RRC Inactive/Idle | Ericsson |
| R1-2112464 | Feature Lead summary #1 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2112465 | Feature Lead summary #2 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2112466 | Feature Lead summary #3 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2112467 | Feature Lead summary #4 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2112645 | DRAFT Reply LS on MCCH change notification | Moderator (BBC) |
| R1-2112646 | Reply LS on MCCH change notification | RAN1, BBC |
| R1-2112715 | Feature Lead summary #5 on RAN basic functions for broadcast/multicast for UEs in RRC_IDLE/RRC_INACTIVE states | Moderator (BBC) |
| R1-2112850 | LS on MTCH scheduling window | RAN1, BBC |
| 8.12.4 | Other | |
| R1-2110898 | Discussion on typical configuration for NR MBS | CHENGDU TD TECH LTD. |
| R1-2110913 | Consideration on potential further enhancement for MBS | ZTE |
| R1-2111042 | Other issues for Rel-17 MBS | vivo |
| R1-2111138 | Other Aspects for Rel-17 MBS | Nokia, Nokia Shanghai Bell |
| R1-2111233 | Discussion on other issues in Rel-17 MBS | CATT |
| R1-2111552 | Discussion on remaining issues for idle and inactive UE | Xiaomi |
| R1-2111917 | Discussion on RRC parameters for NR MBS | Huawei, HiSilicon, CBN |
| R1-2112066 | Other aspects for MBS | LG Electronics |
| R1-2112085 | Discussion on further improvements for MBS | ASUSTeK |
| R1-2112349 | Assumptions for performance evaluations of NR-MBS | Ericsson |
| 8.13 | NR Dynamic spectrum sharing (DSS) | |
| R1-2112441 | Introduction of dynamic spectrum sharing enhancements in NR | Samsung |
| R1-2112479 | Introduction of NR further Multi-RAT Dual-Connectivity enhancements | Nokia |
| R1-2112798 | Session notes for 8.13 (NR Dynamic spectrum sharing (DSS)) | Ad-hoc Chair (CMCC) |
| R1-2112885 | Summary of Email discussion [107-e-R17-RRC-DSS] | Moderator (Ericsson) |
| R1-2112896 | Summary of RAN1 agreements for Rel17 NR DSS WI | WI rapporteur (Ericsson) |
| R1-2112929 | Introduction of dynamic spectrum sharing enhancements in NR | Samsung |
| R1-2112945 | Introduction of NR further Multi-RAT Dual-Connectivity enhancements | Nokia |
| R1-2112962 | Introduction of NR dynamic spectrum sharing | Huawei |
| 8.13.1 | Cross-carrier scheduling (from Scell to Pcell) | |
| R1-2110796 | Discussion on SCell PDCCH scheduling P(S)Cell PDSCH or PUSCH | Huawei, HiSilicon |
| R1-2110924 | Discussion on Cross-Carrier Scheduling from SCell to PCell | ZTE |
| R1-2110944 | On cross-carrier scheduling from SCell to Pcell | Nokia, Nokia Shanghai Bell |
| R1-2111043 | Remaining issues on Scell scheduling Pcell | vivo |
| R1-2111116 | Discussion on cross-carrier scheduling from SCell to Pcell | Spreadtrum Communications |
| R1-2111346 | Discussion on cross-carrier scheduling from Scell to Pcell | OPPO |
| R1-2111519 | On SCell scheduling PCell transmissions | Intel Corporation |
| R1-2111553 | Discussion on cross-carrier scheduling from SCell to PCell | Xiaomi |
| R1-2111631 | Discussion on cross-carrier scheduling from SCell to PCell | CMCC |
| R1-2111764 | Cross-carrier scheduling from SCell to PCell | Samsung |
| R1-2111900 | Views on Rel-17 DSS SCell scheduling Pcell | Apple |
| R1-2111954 | Cross-carrier scheduling (from Scell to Pcell) | Lenovo, Motorola Mobility |
| R1-2111999 | Remaining issues on cross-carrier scheduling from SCell to Pcell | ETRI |
| R1-2112067 | Discussion on cross-carrier scheduling from SCell to Pcell | LG Electronics |
| R1-2112131 | Discussion on cross-carrier scheduling enhancements for NR DSS | NTT DOCOMO, INC. |
| R1-2112154 | Enhanced cross-carrier scheduling for DSS | Ericsson |
| R1-2112242 | Cross-carrier scheduling from an SCell to the PCell/PSCell | Qualcomm Incorporated |
| R1-2112295 | On Cross-Carrier Scheduling from sSCell to P(S)Cell | MediaTek Inc. |
| R1-2112529 | Summary of Email discussion [107-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2112619 | Summary#2 of Email discussion [107-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2112653 | Summary#3 of Email discussion [107-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2112733 | Summary#4 of Email discussion [107-e-NR-DSS-01] | Moderator (Ericsson) |
| R1-2112884 | Summary#5 of Email discussion [107-e-NR-DSS-01] | Moderator (Ericsson) |
| 8.13.2 | Support efficient activation/de-activation mechanism for SCells in NR CA | |
| R1-2110797 | Discussion on efficient activation/de-activation mechanism for SCells | Huawei, HiSilicon |
| R1-2110884 | Support efficient activation/de-activation mechanism for Scells | FUTUREWEI |
| R1-2110925 | Discussion on Support Efficient Activation De-activation Mechanism for SCells in NR CA | ZTE |
| R1-2110945 | On low latency Scell activation | Nokia, Nokia Shanghai Bell |
| R1-2111044 | Remaining issues on efficient activation/de-activation mechanism for Scells | vivo |
| R1-2111347 | Discussion on efficient activation/de-activation for Scell | OPPO |
| R1-2111520 | On efficient activation/de-activation for SCells | Intel Corporation |
| R1-2111554 | Discussion on efficient activation and de-activation mechanism for SCell in NR CA | Xiaomi |
| R1-2111765 | Remaining Issues on Scell Activation/Deactivation | Samsung |
| R1-2111901 | On efficient SCell Activation/Deactivation | Apple |
| R1-2112068 | Discussion on fast and efficient SCell activation in NR CA | LG Electronics |
| R1-2112132 | Discussion on efficient activation deactivation mechanism for Scells | NTT DOCOMO, INC. |
| R1-2112155 | Reduced Latency SCell Activation | Ericsson |
| R1-2112243 | Efficient activation/de-activation mechanism for SCells in NR CA | Qualcomm Incorporated |
| R1-2112605 | Summary#1 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2112606 | Summary#2 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2112855 | Summary#3 of efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2112904 | Summary of agreements for Rel-17 feMR-DC WI | WI rapporteur (Huawei) |
| R1-2112980 | Summary of email discussion [107-e-R17-RRC-NR-DC] on efficient SCell activation/de-activation mechanism of NR CA | Moderator (Huawei) |
| R1-2112981 | Summary of LS on triggering signaling of temporary RS | Moderator (Huawei) |
| R1-2112982 | Draft LS on triggering signalling of temporary RS for SCell activation | Moderator (Huawei) |
| R1-2112983 | LS on triggering signalling of temporary RS for SCell activation | RAN1, Huawei |
| 8.13.3 | Other | |
| R1-2111045 | Discussion on other aspects for DSS | vivo |
| R1-2111555 | Discussion on collision between temporary RS and other signalings | Xiaomi |
| R1-2111919 | Remaining issues on the efficient activation/de-activation mechanism for SCells | Huawei, HiSilicon |
| R1-2112156 | CRS Rate-matching and PDCCH enhancement for DSS | Ericsson |
| 8.14 | Study on XR Evaluations for NR (RAN1) | |
| R1-2112799 | Session notes for 8.14 (Study on XR Evaluations for NR) | Ad-Hoc Chair (CMCC) |
| 8.14.1 | Performance Evaluation Results | |
| R1-2110811 | Performance evaluation results for XR and Cloud Gaming | Huawei, HiSilicon |
| R1-2110885 | XR evaluation results | FUTUREWEI |
| R1-2111046 | Performance evaluation results for XR | vivo |
| R1-2111234 | Evaluation results of XR performance | CATT |
| R1-2111349 | Evaluation results for XR evaluation | OPPO |
| R1-2111351 | Performance Evaluation Results for XR | ZTE, Sanechips |
| R1-2111360 | Evaluation Results for XR | CEWiT |
| R1-2111521 | Performance evaluation results for XR and CG | Intel Corporation |
| R1-2111556 | Performance evaluation result for XR | Xiaomi |
| R1-2111632 | Performance evaluation results for XR | CMCC |
| R1-2111806 | XR Performance Evaluation Results | AT&T |
| R1-2111828 | Performance results in indoor hotspot and dense urban deployments of CG and VR/AR applications | Nokia, Nokia Shanghai Bell |
| R1-2111830 | Performance Evaluation Results for XR | InterDigital, Inc. |
| R1-2111902 | Performance evaluation on XR | Apple |
| R1-2112069 | Performance evaluation results for XR | LG Electronics |
| R1-2112079 | Performance Evaluation Results for XR | China Unicom |
| R1-2112160 | XR performance evaluation results | Ericsson |
| R1-2112175 | Performance evaluation results of XR | ITRI |
| R1-2112244 | Evaluation Results for XR | Qualcomm Incorporated |
| R1-2112296 | Performance Evaluation Results for XR | MediaTek Inc. |
| R1-2112530 | Evaluation Results for XR | Qualcomm Incorporated |
| R1-2112551 | XR performance evaluation results | Ericsson |
| R1-2112572 | Performance results in indoor hotspot and dense urban deployments of CG and VR/AR applications | Nokia, Nokia Shanghai Bell |
| R1-2112573 | Performance evaluation result for XR | Xiaomi |
| R1-2112648 | Evaluation Results for XR | Qualcomm Incorporated |
| R1-2112668 | [DRAFT] TR section - Capacity evaluation | Moderator (vivo) |
| R1-2112669 | [DRAFT] TR section - Mobility evaluation | Moderator (vivo) |
| R1-2112695 | Summary #1 of [107-e-NR-XR-01] discussion on XR performance evaluation results for capacity | Moderator (vivo) |
| R1-2112696 | Summary #1 of [107-e-NR-XR-04] discussion on XR performance evaluation results for mobility | Moderator (vivo) |
| R1-2112704 | XR coverage evaluation Section in TR 38.838 | Moderator (Qualcomm) |
| R1-2112705 | XR power evaluation Section in TR 38.838 | Moderator (Qualcomm) |
| R1-2112720 | Evaluation Results for XR | Qualcomm Incorporated |
| R1-2112722 | [DRAFT#2] TR section - Capacity evaluation | Moderator (vivo) |
| R1-2112723 | [DRAFT#2] TR section - Mobility evaluation | Moderator (vivo) |
| R1-2112809 | TR section for Power Evaluation | Moderator (Qualcomm) |
| R1-2112810 | TR section for Coverage Evaluation | Moderator (Qualcomm) |
| R1-2112812 | TR 38.838 v0.2.0 | Moderator (Qualcomm) |
| R1-2112813 | TR 38.838 v1.0.0 | Moderator (Qualcomm) |
| R1-2112821 | Conclusion section in TR 38.838 | Moderator (Qualcomm) |
| 8.14.2 | Other | |
| R1-2111047 | Potential enhancement areas for XR | vivo |
| R1-2111235 | Potential area of NR enhancement for the support of XR services | CATT |
| R1-2111350 | Discussion on support of XR/CG service | OPPO |
| R1-2111352 | Considerations on Capacity and Power Working Areas for XR | ZTE, Sanechips |
| R1-2111409 | Potential enhancements for XR | Sony |
| R1-2111522 | Potential enhancement areas for XR | Intel Corporation |
| R1-2111690 | Potential enhancements of NR to support XR services | NEC |
| R1-2111766 | Potential enhancements for XR | Samsung |
| R1-2111787 | Discussion on enhancements for XR | Ericsson |
| R1-2111829 | Enhancements for better XR support over NR | Nokia, Nokia Shanghai Bell |
| R1-2111831 | Discussion on remaining issues and enhancements for XR evaluations | InterDigital, Inc. |
| R1-2111903 | Views on enhancements for XR in Rel-18 | Apple |
| R1-2112245 | Potential Enhancements for XR | Qualcomm Incorporated |
| R1-2112299 | Further Potential XR Enhancements | MediaTek Inc. |
| R1-2112405 | TP for Conclusions of TR 38.838 | Huawei, HiSilicon |
| 8.15 | NB-IoT/eMTC support for Non-Terrestrial Network | |
| R1-2111376 | Summary of [107-e-R17-RRC-IoT-NTN] IoT over NTN | Moderator (MediaTek Inc.) |
| R1-2111377 | List of IoT over NTN Rel-17 RRC parameters | Moderator (MediaTek Inc.) |
| R1-2112420 | Introduction of NB-IoT/eMTC support for Non-Terrestrial Networks in 36.213 s00-s05 | Motorola Mobility |
| R1-2112421 | Introduction of NB-IoT/eMTC support for Non-Terrestrial Networks in 36.213 s06-s07 | Motorola Mobility |
| R1-2112422 | Introduction of NB-IoT/eMTC support for Non-Terrestrial Networks in 36.213 s08-s09 | Motorola Mobility |
| R1-2112423 | Introduction of NB-IoT/eMTC support for Non-Terrestrial Networks in 36.213 s10-s13 | Motorola Mobility |
| R1-2112424 | Introduction of NB-IoT/eMTC support for Non-Terrestrial Networks in 36.213 s14-sxx | Motorola Mobility |
| R1-2112436 | Introduction of NB-IoT/eMTC support in Non-Terrestrial Networks | Ericsson |
| R1-2112800 | Session notes for 8.15 (Study on NB-IoT/eMTC support for Non-Terrestrial Network) | Ad-Hoc Chair (Huawei) |
| R1-2112891 | 3GPP TSG-RAN WG1 Agreements for Release-17 IoT NTN (post RAN1#107-e) | WI rapporteur (MediaTek) |
| R1-2112909 | Introduction of NB-IoT/eMTC support for Non-Terrestrial Networks in 36.213 s00-s05 | Motorola Mobility |
| R1-2112910 | Introduction of NB-IoT/eMTC support for Non-Terrestrial Networks in 36.213 s06-s07 | Motorola Mobility |
| R1-2112911 | Introduction of NB-IoT/eMTC support for Non-Terrestrial Networks in 36.213 s08-s09 | Motorola Mobility |
| R1-2112912 | Introduction of NB-IoT/eMTC support for Non-Terrestrial Networks in 36.213 s10-s13 | Motorola Mobility |
| R1-2112913 | Introduction of NB-IoT/eMTC support for Non-Terrestrial Networks in 36.213 s14-sxx | Motorola Mobility |
| R1-2112925 | Introduction of NB-IoT/eMTC support in Non-Terrestrial Networks | Ericsson |
| 8.15.1 | Enhancements to time and frequency synchronization | |
| R1-2110808 | Discussion on time and frequency synchronization enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2111048 | Remaining issues on time and frequency synchronization enhancements for NB-IoT/eMTC over NTN | vivo |
| R1-2111117 | Discussion on enhancements to time and frequency synchronization for IOT NTN | Spreadtrum Communications |
| R1-2111172 | Enhancements to time and frequency synchronization | Mavenir |
| R1-2111182 | Enhancements to time and frequency synchronization for IoT NTN | NEC |
| R1-2111236 | Time and frequency synchronization enhancement for IoT over NTN | CATT |
| R1-2111276 | Enhancement to time and frequency synchronization for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2111319 | Discussion on enhancements to time and frequency synchronization | OPPO |
| R1-2111373 | Enhancements to time and frequency synchronization for IoT NTN | MediaTek Inc. |
| R1-2111375 | Summary #1 of AI 8.15.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek Inc.) |
| R1-2111410 | Remaining issues on time and frequency synchronisation for IoT-NTN | Sony |
| R1-2111420 | On time and frequency synchronization enhancements for IoT NTN | Ericsson |
| R1-2111451 | Enhancements to time and frequency synchronization | Qualcomm Incorporated |
| R1-2111523 | Remaining issues on synchronization for IoT NTN | Intel Corporation |
| R1-2111557 | Discussion on time and frequency synchronization for IoT NTN | Xiaomi |
| R1-2111633 | Enhancements on time and frequency synchronization for IoT NTN | CMCC |
| R1-2111662 | Discussion on synchronization for IoT-NTN | ZTE |
| R1-2111767 | On enhancements to time and frequency synchronization | Samsung |
| R1-2111904 | Time and Frequency Synchronization in IoT NTN | Apple |
| R1-2112002 | Time and frequency synchronization for IoT NTN | Lenovo, Motorola Mobility |
| R1-2112329 | Enhancements to time and frequency synchronization | Nordic Semiconductor ASA |
| R1-2112531 | On time and frequency synchronization enhancements for IoT NTN | Ericsson |
| R1-2112615 | Summary #2 of AI 8.15.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek Inc.) |
| R1-2112679 | Summary #3 of AI 8.15.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek) |
| R1-2112689 | DRAFT LS on DL synchronization enhancements for IoT NTN | Moderator (MediaTek) |
| R1-2112768 | LS on DL synchronization enhancements for IoT NTN | RAN1, MediaTek |
| R1-2112803 | Summary #4 of AI 8.15.1 Enhancements to time and frequency synchronization for IoT NTN | Moderator (MediaTek) |
| R1-2112847 | DRAFT LS on GNSS Validity duration for IoT NTN | Moderator (MediaTek) |
| R1-2112848 | LS on GNSS Validity duration for IoT NTN | RAN1, MediaTek |
| 8.15.2 | Timing relationship enhancements | |
| R1-2110809 | Discussion on timing relationship enhancement for IoT in NTN | Huawei, HiSilicon |
| R1-2111049 | Remaining issues on timing relationship enhancements for NB-IoT/eMTC over NTN | vivo |
| R1-2111118 | Discussion on timing relationship enhancements for IOT NTN | Spreadtrum Communications |
| R1-2111173 | Timing relationship enhancements | Mavenir |
| R1-2111183 | Timing relationship enhancements for IoT NTN | NEC |
| R1-2111237 | Timing relationship enhancement for IoT over NTN | CATT |
| R1-2111277 | Timing relationship enhancements for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2111320 | Discussion on timing relationship enhancements | OPPO |
| R1-2111374 | Timing relationship enhancements for IoT NTN | MediaTek Inc. |
| R1-2111411 | Remaining issues on timing relationship enhancements for IoT-NTN | Sony |
| R1-2111421 | On timing relationship enhancements for IoT NTN | Ericsson |
| R1-2111452 | Timing relationship enhancements | Qualcomm Incorporated |
| R1-2111524 | Remaining issues on timing relationships for IoT NTN | Intel Corporation |
| R1-2111558 | Discussion on the timing relationship enhancement for IoT NTN | Xiaomi |
| R1-2111634 | Discussion on timing relationship enhancements for IoT NTN | CMCC |
| R1-2111663 | Discussion on timing relationship for IoT-NTN | ZTE |
| R1-2111768 | Timing relationship enhancements | Samsung |
| R1-2111905 | Timing Relationship Enhancements in IoT NTN | Apple |
| R1-2112003 | Timing Relationship for IoT NTN | Lenovo, Motorola Mobility |
| R1-2112331 | Timing relationship enhancements | Nordic Semiconductor ASA |
| R1-2112552 | FL summary 1 of AI 8.15.2 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2112553 | FL summary 2 of AI 8.15.2 Timing relationship for IoT-NTN | Moderator (Sony) |
| R1-2112554 | FL summary 3 of AI 8.15.2 Timing relationship for IoT-NTN | Moderator (Sony) |
| 8.15.3 | Other | |
| R1-2111278 | Discussion on other aspects for NB-IoT/eMTC over NTN | Nokia, Nokia Shanghai Bell |
| R1-2111422 | Mobile IoT in the 5G future – NB-IoT and eMTC for NTN | Ericsson |
| R1-2111559 | Discussion on the other design aspects for IoT NTN | Xiaomi |
| R1-2111664 | Discussion on additional enhancement for IoT-NTN | ZTE |
| R1-2111925 | Other aspects to support IoT in NTN | Huawei, HiSilicon |
| 8.16 | Rel-17 UE Features | |
| R1-2111378 | 3GPP TSG-RAN WG1 Agreements for Release-17 IoT NTN (post RAN1#107-e) | Moderator (MediaTek Inc.) |
| R1-2112819 | Session Notes for 8.16 (Rel-17 UE Features) | Ad Hoc Chair (NTT DOCOMO) |
| R1-2112900 | Updated RAN1 UE features list for Rel-17 LTE after RAN1 #107-e | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2112901 | LS on updated Rel-17 RAN1 UE features list for LTE | RAN1, AT&T, NTT DOCOMO, INC. |
| R1-2112902 | Updated RAN1 UE features list for Rel-17 NR after RAN1 #107-e | Moderators (AT&T, NTT DOCOMO, INC.) |
| R1-2112903 | LS on updated Rel-17 RAN1 UE features list for NR | RAN1, AT&T, NTT DOCOMO, INC. |
| 8.16.1 | UE features for further enhancements on NR-MIMO | |
| R1-2110788 | Rel-17 UE features for further NR MIMO enhancements | Huawei, HiSilicon |
| R1-2110962 | UE features for feMIMO | ZTE |
| R1-2111050 | Discussion Rel-17 MIMO UE features | vivo |
| R1-2111152 | On UE features for further enhancements on NR-MIMO | Nokia, Nokia Shanghai Bell |
| R1-2111286 | UE features for further enhancements on NR-MIMO | OPPO |
| R1-2111460 | Discussion on Rel-17 UE feature for NR FeMIMO | LG Electronics |
| R1-2111525 | On UE features for feMIMO | Intel Corporation |
| R1-2111560 | Discussion on Rel-17 FeMIMO UE Features | Xiaomi |
| R1-2111635 | Discussion on FeMIMO UE features | CMCC |
| R1-2111671 | Discussion on UE features for FeMIMO | Ericsson |
| R1-2111769 | UE features for Rel-17 NR FeMIMO | Samsung |
| R1-2111807 | Summary of UE features for further enhancements on NR-MIMO | Moderator (AT&T) |
| R1-2111906 | Views on Rel-17 FeMIMO UE features | Apple |
| R1-2111955 | Discussion on UE features for FeMIMO | Lenovo, Motorola Mobility |
| R1-2112246 | Discussion on FeMIMO UE features | Qualcomm Incorporated |
| R1-2112282 | UE Features for further enhancements on NR MIMO | MediaTek Inc. |
| R1-2112774 | Session Notes of AI 8.16.1 | Ad-Hoc Chair (AT&T) |
| 8.16.2 | UE features for supporting NR from 52.6 GHz to 71 GHz | |
| R1-2110833 | Rel-17 UE features for extension to 71 GHz | Huawei, HiSilicon |
| R1-2111051 | Discussions on UE features for NR operation from 52.6GHz to 71GHz | vivo |
| R1-2111081 | Discussion on UE features for 52.6 to 71GHz | ZTE, Sanechips |
| R1-2111153 | On UE features for supporting NR from 52.6 GHz to 71 GHz | Nokia, Nokia Shanghai Bell |
| R1-2111313 | Discussion on UE features for FR2-2 | OPPO |
| R1-2111471 | UE features for extending current NR operation to 71 GHz | Ericsson |
| R1-2111526 | Discussion on UE capability for extending NR up to 71 GHz | Intel Corporation |
| R1-2111770 | UE features for supporting NR from 52.6 GHz to 71 GHz | Samsung |
| R1-2111808 | Summary of UE features for supporting NR from 52.6 GHz to 71 GHz | Moderator (AT&T) |
| R1-2111907 | Views on Rel-17 Above 52.6 GHz UE features | Apple |
| R1-2112070 | Discussion on UE features for NR above 52.6 GHz | LG Electronics |
| R1-2112133 | Views on UE features for supporting NR from 52.6 GHz to 71 GHz | NTT DOCOMO, INC. |
| R1-2112247 | UE features for NR from 52.6 Ghz to 71 Ghz | Qualcomm Incorporated |
| R1-2112304 | Views on UE features for supporting NR from 52.6 GHz to 71 GHz | MediaTek Inc. |
| R1-2112439 | UE features for extending current NR operation to 71 GHz | Ericsson |
| R1-2112775 | Session Notes of AI 8.16.2 | Ad-Hoc Chair (AT&T) |
| 8.16.3 | UE features for enhanced IIoT and and URLLC | |
| R1-2110821 | Rel-17 UE features for URLLC | Huawei, HiSilicon |
| R1-2110926 | Discussion on UE features for enhanced IIoT and URLLC | ZTE |
| R1-2111052 | Discussion on UE features for IIoT and URLLC | vivo |
| R1-2111154 | On UE features for enhanced IIoT and and URLLC | Nokia, Nokia Shanghai Bell |
| R1-2111192 | Rel-17 UE Features for IIoT/URLLC | Ericsson |
| R1-2111345 | Discussion on UE features for IIoT and URLLC | OPPO |
| R1-2111527 | Discussion on UE capability for URLLC/IIOT | Intel Corporation |
| R1-2111771 | UE features for IIoT/URLLC | Samsung |
| R1-2111908 | View on Rel-17 UE features for enhanced IIoT and and URLLC | Apple |
| R1-2112134 | Discussion on Rel.17 UE features for enhanced IIoT/URLLC | NTT DOCOMO, INC. |
| R1-2112135 | Summary on UE features for enhanced IIoT and and URLLC | Moderator (NTT DOCOMO, INC.) |
| R1-2112248 | UE features for enhanced IIOT and URLLC | Qualcomm Incorporated |
| R1-2112288 | Views on UE features for enhanced IIoT and URLLC | MediaTek Inc. |
| 8.16.4 | UE features for NR NTN | |
| R1-2110807 | Rel-17 UE features for NR NTN | Huawei, HiSilicon |
| R1-2111155 | On UE features for NR NTN | Nokia, Nokia Shanghai Bell |
| R1-2111318 | Discussion on UE features for NTN-NR | OPPO |
| R1-2111417 | On UE features for NR NTN | Ericsson |
| R1-2111528 | On UE features for NR NTN | Intel Corporation |
| R1-2111665 | Discussion on UE feature for NR-NTN | ZTE |
| R1-2111772 | UE features for NR NTN | Samsung |
| R1-2111809 | Summary of UE features for NR NTN | Moderator (AT&T) |
| R1-2111909 | Views on Rel-17 NR NTN UE features | Apple |
| R1-2111972 | Discussion on Rel-17 UE feature for NR NTN | LG Electronics |
| R1-2112249 | UE features for NR NTN | Qualcomm Incorporated |
| R1-2112272 | Discussion on UE features for NTN | Beijing Xiaomi Mobile Software |
| 8.16.5 | UE features for NR positioning enhancements | |
| R1-2110855 | Rel-17 UE features for positioning enhancements | Huawei, HiSilicon |
| R1-2110963 | UE features for NR positioning enhancements | ZTE |
| R1-2111053 | Discussion on UE features for NR positioning enhancements | vivo |
| R1-2111156 | On UE features for NR positioning enhancements | Nokia, Nokia Shanghai Bell |
| R1-2111239 | Further discussion on Rel-17 UE features for NR Positioning enhancements | CATT |
| R1-2111295 | UE features for NR positioning enhancements | OPPO |
| R1-2111529 | UE Features for NR Positioning Enhancements | Intel Corporation |
| R1-2111773 | UE features for NR positioning enhancements | Samsung |
| R1-2111810 | Summary of UE features for NR positioning enhancements | Moderator (AT&T) |
| R1-2112250 | Discussion on Positioning Enhancements Features | Qualcomm Incorporated |
| R1-2112338 | Views on NR positioning enhancements UE features | Ericsson |
| R1-2112776 | Session Notes of AI 8.16.5 | Ad-Hoc Chair (AT&T) |
| 8.16.6 | UE features for REDCAP | |
| R1-2110773 | UE features for RedCap | Ericsson |
| R1-2110803 | Rel-17 UE features for RedCap | Huawei, HiSilicon |
| R1-2110893 | Further discussion on UE features for REDCAP | FUTUREWEI |
| R1-2111054 | Discussion on UE feature for NR REDCAP | vivo, Guangdong Genius |
| R1-2111072 | Discussion on RedCap UE features | ZTE, Sanechips |
| R1-2111119 | UE features for RedCap | Spreadtrum Communications |
| R1-2111157 | On UE features for REDCAP | Nokia, Nokia Shanghai Bell |
| R1-2111333 | Rel-17 RedCap UE features | OPPO |
| R1-2111530 | On UE features for RedCap | Intel Corporation |
| R1-2111562 | Discussion on Rel-17 UE features on RedCap | Xiaomi |
| R1-2111636 | Discussion on UE features for RedCap | CMCC |
| R1-2111774 | UE feature for RedCap | Samsung |
| R1-2111910 | UE features for RedCap | Apple |
| R1-2111959 | Discussion on UE feature of RedCap | NEC |
| R1-2112136 | Discussion on UE features for RedCap | NTT DOCOMO, INC. |
| R1-2112137 | Summary on UE features for REDCAP | Moderator (NTT DOCOMO, INC.) |
| R1-2112251 | UE features for RedCap | Qualcomm Incorporated |
| R1-2112289 | Views on UE features for RedCap | MediaTek Inc. |
| R1-2112503 | FL summary on LS on capability related RAN2 agreements for RedCap | Moderator (Ericsson) |
| R1-2112753 | [Draft] Reply LS on capability related RAN2 agreements for RedCap | Ericsson |
| R1-2112754 | Reply LS on capability related RAN2 agreements for RedCap | RAN1, Ericsson |
| 8.16.7 | UE features for UE power saving enhancements | |
| R1-2110841 | Rel-17 UE features for UE power saving enhancements | Huawei, HiSilicon |
| R1-2110943 | Discussion on UE feature for UE power saving enhancements | ZTE, Sanechips |
| R1-2111055 | Discussion on UE features for UE power saving enhancements | vivo |
| R1-2111158 | On UE features for UE power saving enhancements | Nokia, Nokia Shanghai Bell |
| R1-2111240 | Discussion on UE feature of UE Power saving enhancements for NR | CATT |
| R1-2111531 | Discussion on UE features for UE power saving | Intel Corporation |
| R1-2111775 | UE features for UE power saving enhancements | Samsung |
| R1-2111911 | Views on UE features for Rel-17 UE power saving | Apple |
| R1-2112138 | Discussion on Rel-17 UE features for UE power saving | NTT DOCOMO, INC. |
| R1-2112139 | Summary on UE features for UE power saving enhancements | Moderator (NTT DOCOMO, INC.) |
| R1-2112157 | UE features for UEPS | Ericsson |
| R1-2112252 | UE features for UE power saving enhancements | Qualcomm Incorporated |
| R1-2112297 | On UE features for UE power saving enhancements | MediaTek Inc. |
| 8.16.8 | UE features for NR coverage enhancement | |
| R1-2110794 | Rel-17 UE features for NR coverage enhancement | Huawei, HiSilicon |
| R1-2110927 | Discussion on UE features for NR coverage enhancement | ZTE |
| R1-2111056 | Discussion on UE features for NR coverage enhancement | vivo |
| R1-2111159 | On UE features for NR coverage enhancement | Nokia, Nokia Shanghai Bell |
| R1-2111532 | Discussion on UE features for NR coverage enhancement | Intel Corporation |
| R1-2111776 | UE features for NR coverage enhancement | Samsung |
| R1-2111912 | Views on Rel-17 Coverage Enhancement UE Features | Apple |
| R1-2112041 | UE Features for NR Coverage Enhancement | Ericsson |
| R1-2112140 | Discussion on Rel.17 UE features for NR coverage enhancement | NTT DOCOMO, INC. |
| R1-2112141 | Summary on UE features for NR coverage enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2112168 | UE feature for Rel-17 coverage enhancement | Sharp |
| R1-2112253 | UE Features for Coverage Enhancements | Qualcomm Incorporated |
| R1-2112319 | Discussion on UE features for NR Coverage Enhancement | MediaTek Inc. |
| 8.16.9 | UE features for NB-IoT and LTE-MTC enhancements | |
| R1-2110859 | Rel-17 UE features for NB-IoT and LTE-MTC enhancements | Huawei, HiSilicon |
| R1-2111073 | Discussion on LTE-M and NB-IoT UE features | ZTE, Sanechips |
| R1-2111160 | On UE features for NB-IoT and LTE-MTC enhancements | Nokia, Nokia Shanghai Bell |
| R1-2112142 | Summary on UE features for NB-IoT and LTE-MTC enhancements | Moderator (NTT DOCOMO, INC.) |
| R1-2112254 | UE features for NB-IoT and LTE-MTC enhancements | Qualcomm Incorporated |
| R1-2112364 | On UE features for NB-IoT and LTE-MTC enhancements | Ericsson |
| 8.16.10 | UE features for IAB enhancements | |
| R1-2110836 | Rel-17 UE features for IAB | Huawei, HiSilicon |
| R1-2111057 | Discussion on UE features for IAB | vivo |
| R1-2111161 | On UE features for IAB enhancements | Nokia, Nokia Shanghai Bell |
| R1-2111533 | UE features for IAB | Intel Corporation |
| R1-2111594 | Discussion on NR Rel-17 IAB MT Features | ZTE, Sanechips |
| R1-2111777 | UE features for NR IAB | Samsung |
| R1-2111811 | Summary of UE features for IAB enhancements | Moderator (AT&T) |
| R1-2111956 | Discussion on UE features for IAB enhancements | Lenovo, Motorola Mobility |
| R1-2112359 | UE features for enhanced IAB | Ericsson |
| 8.16.11 | UE features for NR sidelink enhancement | |
| R1-2110846 | Rel-17 UE features for NR sidelink enhancement | Huawei, HiSilicon |
| R1-2110888 | UE features for NR sidelink enhancement | FUTUREWEI |
| R1-2111058 | UE features for NR sidelink enhancement | vivo |
| R1-2111238 | Further discussion on Rel-17 UE features for sidelink enhancements | CATT, GOHIGH |
| R1-2111302 | On UE feature list for NR sidelink enhancement | OPPO |
| R1-2111534 | UE Features for NR Sidelink Enhancements | Intel Corporation |
| R1-2111561 | Discussion on Rel-17 UE features on sidelink enhancement | Xiaomi |
| R1-2111638 | Discussion on UE features for NR sidelink enhancement | ZTE, Sanechips |
| R1-2111778 | UE features for NR sidelink enhancement | Samsung |
| R1-2111913 | Views on Rel-17 NR Sidelink UE Features | Apple |
| R1-2112143 | Discussion on Rel.17 UE features for NR SL enhancement | NTT DOCOMO, INC. |
| R1-2112144 | Summary on UE features for NR sidelink enhancement | Moderator (NTT DOCOMO, INC.) |
| R1-2112256 | UE Features for Sidelink Enhancements | Qualcomm Incorporated |
| R1-2112306 | Views on UE features for NR sidelink enhancements | MediaTek Inc. |
| R1-2112354 | UE features for NR sidelink enhancement | Ericsson |
| 8.16.12 | UE features for NR MBS | |
| R1-2110780 | Rel-17 UE features for NR MBS | Huawei, HiSilicon, CBN |
| R1-2110928 | Discussion on Rel-17 UE features for NR MBS | ZTE |
| R1-2111059 | Discussion on UE features for MBS | vivo |
| R1-2111120 | UE features for R17 NR MBS | Spreadtrum Communications |
| R1-2111162 | On UE features for NR MBS | Nokia, Nokia Shanghai Bell |
| R1-2111306 | Discussion on UE features for NR MBS | OPPO |
| R1-2111535 | Discussion on UE Features for NR MBS | Intel Corporation |
| R1-2111779 | UE features for NR MBS | Samsung |
| R1-2111914 | Views on Rel-17 MBS UE features | Apple |
| R1-2112145 | Summary on UE features for NR MBS | Moderator (NTT DOCOMO, INC.) |
| R1-2112257 | UE features for MBS | Qualcomm Incorporated |
| R1-2112315 | Views on UE features for NR MBS | MediaTek Inc. |
| R1-2112345 | views on NR MBS UE features | Ericsson |
| 8.16.13 | UE features for DSS | |
| R1-2110798 | Rel-17 UE features for DSS and MR-DC | Huawei, HiSilicon |
| R1-2110929 | Discussion on Rel-17 UE features for DSS | ZTE |
| R1-2111060 | Discussion on UE features for DSS | vivo |
| R1-2111163 | On UE features for DSS and LTE NR DC enhancements | Nokia, Nokia Shanghai Bell |
| R1-2111348 | Discussion on UE features for DSS | OPPO |
| R1-2111536 | UE features for DSS | Intel Corporation |
| R1-2111780 | UE features for DSS | Samsung |
| R1-2111812 | Summary of UE features for DSS | Moderator (AT&T) |
| R1-2111915 | Views on Rel-17 DSS UE features | Apple |
| R1-2112158 | UE features for DSS and CA Enhancements | Ericsson |
| R1-2112258 | UE features for DSS and LTE_NR_DC_enh2 | Qualcomm Incorporated |
| R1-2112298 | On UE features for DSS | MediaTek Inc. |
| 8.16.14 | UE features for IoT over NTN | |
| R1-2110810 | Rel-17 UE features for NTN IoT | Huawei, HiSilicon |
| R1-2111164 | On UE features for IoT over NTN | Nokia, Nokia Shanghai Bell |
| R1-2111321 | Discussion on UE features for NTN-IoT | OPPO |
| R1-2111423 | On UE features for IoT over NTN | Ericsson |
| R1-2111537 | On UE features for IOT over NTN | Intel Corporation |
| R1-2111666 | Discussion on UE feature for IoT-NTN | ZTE |
| R1-2111781 | UE features for IoT over NTN | Samsung |
| R1-2111813 | Summary of UE features for IoT over NTN | Moderator (AT&T) |
| R1-2111916 | Views on Rel-17 IoT over NTN UE features | Apple |
| R1-2112255 | UE features for IoT over NTN | Qualcomm Incorporated |
| R1-2112259 | UE features for IoT over NTN | Qualcomm Incorporated |
| R1-2112273 | Discussion on UE features for IoT NTN | Beijing Xiaomi Mobile Softwar |
| 8.16.15 | UE features for LTE based 5G terrestrial broadcast | |
| R1-2110871 | Rel-17 UE features for LTE based 5G terrestrial broadcast | Huawei, HiSilicon |
| R1-2110930 | Discussion on Rel-17 UE features for LTE based 5G terrestrial broadcast | ZTE |
| R1-2111165 | On UE features for LTE based 5G terrestrial broadcast | Nokia, Nokia Shanghai Bell |
| R1-2112146 | Summary on UE features for LTE based 5G terrestrial broadcast | Moderator (NTT DOCOMO, INC.) |
| R1-2112260 | UE features for LTE-based 5G terrestrial broadcast | Qualcomm Incorporated |
| 8.16.16 | UE features for DL 1024QAM for NR FR1 | |
| R1-2110849 | Rel-17 UE features for DL 1024QAM for NR FR1 | Huawei, HiSilicon |
| R1-2110942 | Discussion on UE feature for 1024QAM | ZTE, Sanechips |
| R1-2111166 | On UE features for DL 1024QAM for NR FR1 | Nokia, Nokia Shanghai Bell |
| R1-2111782 | UE features for DL 1024QAM | Samsung |
| R1-2111814 | Summary of UE features for DL 1024QAM for NR FR1 | Moderator (AT&T) |
| R1-2112159 | UE features for 1024QAM | Ericsson |
| R1-2112261 | UE features for DL 1024 QAM for NR FR1 | Qualcomm Incorporated |
| 8.16.17 | Other | |
| R1-2110800 | Rel-17 UE features for UL Tx switching | Huawei, HiSilicon |
| R1-2110931 | Discussion on Rel-17 UE features for UL Tx switching | ZTE |
| R1-2111167 | On Remaining Rel-17 UE features | Nokia, Nokia Shanghai Bell |
| R1-2112147 | Summary on other UE feature related discussions | Moderator (NTT DOCOMO, INC.) |
| R1-2112262 | UE features for Rel-17 UL Tx switching | Qualcomm Incorporated |
| 8.17 | Other | |
| R1-2110856 | Enhancements on the scheduling of PUSCH | Huawei, HiSilicon, Ericsson, China Unicom |
| R1-2111061 | Rel-17 TEI proposal | vivo |
| R1-2111174 | TEI-17 proposal targeting the false PMI reporting issue | Ericsson |
| R1-2111287 | Support of default power control parameter per TRP | OPPO |
| R1-2111538 | Rel-17 TEI proposal for mitigating half-duplex issue in NR V2X groupcast NACK-only case | Intel Corporation, NTT DOCOMO, Qualcomm, Ericsson, Bosch |
| R1-2112000 | Rel-17 TEI proposals on SSB resource for RLM and HARQ-ACK feedback enhancements for TDD-FDD CA | CATT |
| R1-2112148 | Summary on Rel-17 TEIs | Moderator (NTT DOCOMO, INC.) |
| R1-2112263 | Rel-17 TEI | Qualcomm Incorporated |
| R1-2112416 | Introduction of New bands and bandwidth allocation for LTE based 5G terrestrial broadcast in 36.213 s10-s13 | Motorola Mobility |
| R1-2112427 | TEI17: Introduction of Timing advance (TA) PRACH based solution for NR UL E-CID | Intel Corporation |
| R1-2112437 | Introduction of new bandwidths for LTE-based 5G terrestrial broadcast | Ericsson |
| R1-2112438 | Introduction of DL 1024QAM for NR FR1 | Ericsson |
| R1-2112469 | Introduction of NR DL 1024QAM for FR1 | Huawei |
| R1-2112481 | Introduction of DL 1024QAM for NR FR1 | Nokia |
| R1-2112489 | Introduction of UL Tx Switching enhancements | Nokia |
| R1-2112516 | Introduction of DL 1024QAM | NTT DOCOMO |
| R1-2112905 | Introduction of New bands and bandwidth allocation for LTE based 5G terrestrial broadcast in 36.213 s10-s13 | Motorola Mobility |
| R1-2112916 | TEI17: Introduction of Timing advance (TA) PRACH based solution for NR UL E-CID | Intel Corporation |
| R1-2112926 | Introduction of new bandwidths for LTE-based 5G terrestrial broadcast | Ericsson |
| R1-2112927 | Introduction of DL 1024QAM for NR FR1 | Ericsson |
| R1-2112938 | Introduction of NR DL 1024QAM for FR1 | Huawei |
| R1-2112947 | Introduction of DL 1024QAM for NR FR1 | Nokia |
| R1-2112955 | Introduction of UL Tx Switching enhancements | Nokia |
| R1-2112961 | Introduction of DL 1024QAM | NTT DOCOMO |